eclipse-platform / eclipse.platform.releng Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 22.0 7.01 MB

eclipse.platform.releng's People

Contributors

Stargazers

Watchers

eclipse.platform.releng's Issues

Plan for 2023-06 (4.28) release

Continuation of eclipse-platform/eclipse.platform.releng.aggregator#1225 for 4.28 release.

As of today, https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_28.xml shows 404 error.

Here is how it should look like:
https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_27.xml

Missing category for "Bytecode Outline View" and "Java AST View"

When installing the Bytecode Outline View or the Java AST View via Help > Install New Software..., Group items by category has to be disabled, otherwise they will not be listed.

This applies to both, the update sites of the Eclipse project, e.g. https://download.eclipse.org/eclipse/updates/latest, and the Eclipse Simultaneous Release update sites, e.g. https://download.eclipse.org/releases/latest. For the latter, I would guess that this would in org.eclipse.simrel.build.git require editing both ep.aggrcon and simrel.aggr.

Features not in a category:

Bytecode Outline View - org.eclipse.jdt.bcoview.feature.feature.group
Java AST View - org.eclipse.jdt.astview.feature.feature.group

Import-Package and other requirements not translated as Maven dependencies when generating pom

Currently, the pom generator (CBI p2Repo aggregator) only process Require-Bundle to derive Maven dependencies. Many bundles, more and more, do use Import-Package or even Require-Capability to define runtime requirements. Those should also be resolved and translated to Maven dependencies when generating the pom file to be deployed.

4.28 I-Build: I20230330-0240 - BUILD FAILED

See https://www.eclipse.org/lists/platform-releng-dev/msg39231.html
https://ci.eclipse.org/releng/job/Builds/job/I-build-4.28/36/consoleText

Most likely caused by the previous IBuild that was broken via eclipse-pde/eclipse.pde#536.

We have a fix for that already, via eclipse-pde/eclipse.pde#542 but I ssuppose the SDK build uses previous one to build itself.

So I'm going to declare https://download.eclipse.org/eclipse/downloads/drops4/I20230329-1800/ build as unstable via https://ci.eclipse.org/releng/job/Builds/job/markUnstable/

Failing of test SimplePerformanceMeterTest.testPerformanceMeterFactory

The following tests are in conflict and one of them always fails (the one that runs the last).

org.eclipse.test.internal.performance.tests.SimplePerformanceMeterTest.testPerformanceMeterFactory()
org.eclipse.test.internal.performance.tests.PerformanceMeterFactoryTest.testPerformanceMeterFactory()

java.lang.IllegalArgumentException
	at org.eclipse.test.internal.performance.PerformanceMeterFactory.assertUniqueScenario(PerformanceMeterFactory.java:46)
	at org.eclipse.test.internal.performance.PerformanceMeterFactory.createPerformanceMeter(PerformanceMeterFactory.java:30)
	at org.eclipse.test.performance.Performance.createPerformanceMeter(Performance.java:159)
	at org.eclipse.test.internal.performance.tests.SimplePerformanceMeterTest.testPerformanceMeterFactory(SimplePerformanceMeterTest.java:26)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at junit.framework.TestCase.runTest(TestCase.java:177)
	at junit.framework.TestCase.runBare(TestCase.java:142)
	at junit.framework.TestResult$1.protect(TestResult.java:122)
	at junit.framework.TestResult.runProtected(TestResult.java:142)
	at junit.framework.TestResult.run(TestResult.java:125)
	at junit.framework.TestCase.run(TestCase.java:130)
	at junit.framework.TestSuite.runTest(TestSuite.java:241)
	at junit.framework.TestSuite.run(TestSuite.java:236)
	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
	at org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
	at org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:147)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:127)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:90)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:55)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:102)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:54)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:114)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:95)
	at org.junit.platform.launcher.core.DefaultLauncherSession$DelegatingLauncher.execute(DefaultLauncherSession.java:91)
	at org.junit.platform.launcher.core.SessionPerRequestLauncher.execute(SessionPerRequestLauncher.java:60)
	at org.eclipse.jdt.internal.junit5.runner.JUnit5TestReference.run(JUnit5TestReference.java:98)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:40)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:529)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:756)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:452)
	at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:74)
	at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.start(CoreTestApplication.java:28)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1440)

Maven snapshots are not properly published

See for example https://repo.eclipse.org/content/repositories/eclipse-snapshots/org/eclipse/platform/org.eclipse.equinox.p2.publisher.eclipse/ is empty.

Windows tests are not executed since Jan 20, 2023

Since few days tests on Windows are simply not executed because they fail to start.

Last working: https://ci.eclipse.org/releng/view/Builds/job/AutomatedTests/job/ep427I-unit-win32-java17/18/

First failing: Build 19 (Jan 20, 2023, 4:00:55 PM) https://ci.eclipse.org/releng/view/Builds/job/AutomatedTests/job/ep427I-unit-win32-java17/19/

See https://ci.eclipse.org/releng/view/Builds/job/AutomatedTests/job/ep427I-unit-win32-java17/

Most recent console:
https://ci.eclipse.org/releng/view/Builds/job/AutomatedTests/job/ep427I-unit-win32-java17/26/console

C:\Users\genie.releng\workspace\AutomatedTests\ep427I-unit-win32-java17>ant -f getEBuilder.xml -Djava.io.tmpdir=C:\Users\genie.releng\workspace\AutomatedTests\ep427I-unit-win32-java17\tmp -Djvm="C:\PROGRA~1\ECLIPS~1\jdk-17.0.5.8-hotspot\bin\java.exe" -DbuildId=I20230125-0250  -DeclipseStream= "4.27.0" -DEBUILDER_HASH= "859ef946010986ebfff38d88759c674162116a7c"  -DdownloadURL="https://download.eclipse.org/eclipse/downloads/drops4/I20230125-0250" -Dargs=all -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -DtestSuite=all 
ANT_OPTS is set to  -Djava.security.manager=allow
Usage: java [options] <mainclass> [args...]
           (to execute a class)
   or  java [options] -jar <jarfile> [args...]
           (to execute a jar file)
   or  java [options] -m <module>[/<mainclass>] [args...]
       java [options] --module <module>[/<mainclass>] [args...]
           (to execute the main class in a module)
   or  java [options] <sourcefile> [args]
           (to execute a single source-file program)

 Arguments following the main class, source file, -jar <jarfile>,
 -m or --module <module>/<mainclass> are passed as the arguments to
 main class.

 where options include:

    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
    --class-path <class search path of directories and zip/jar files>
                  A ; separated list of directories, JAR archives,
                  and ZIP archives to search for class files.
    -p <module path>
    --module-path <module path>...
                  A ; separated list of directories, each directory
                  is a directory of modules.
    --upgrade-module-path <module path>...
                  A ; separated list of directories, each directory
                  is a directory of modules that replace upgradeable
                  modules in the runtime image
    --add-modules <module name>[,<module name>...]
                  root modules to resolve in addition to the initial module.
                  <module name> can also be ALL-DEFAULT, ALL-SYSTEM,
                  ALL-MODULE-PATH.
    --enable-native-access <module name>[,<module name>...]
                  modules that are permitted to perform restricted native operations.
                  <module name> can also be ALL-UNNAMED.
    --list-modules
                  list observable modules and exit
    -d <module name>
    --describe-module <module name>
                  describe a module and exit
    --dry-run     create VM and load main class but do not execute main method.
                  The --dry-run option may be useful for validating the
                  command-line options such as the module system configuration.
    --validate-modules
                  validate all modules and exit
                  The --validate-modules option may be useful for finding
                  conflicts and other errors with modules on the module path.
    -D<name>=<value>
                  set a system property
    -verbose:[class|module|gc|jni]
                  enable verbose output for the given subsystem
    -version      print product version to the error stream and exit
    --version     print product version to the output stream and exit
    -showversion  print product version to the error stream and continue
    --show-version
                  print product version to the output stream and continue
    --show-module-resolution
                  show module resolution output during startup
    -? -h -help
                  print this help message to the error stream
    --help        print this help message to the output stream
    -X            print help on extra options to the error stream
    --help-extra  print help on extra options to the output stream
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
                  enable assertions with specified granularity
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
                  disable assertions with specified granularity
    -esa | -enablesystemassertions
                  enable system assertions
    -dsa | -disablesystemassertions
                  disable system assertions
    -agentlib:<libname>[=<options>]
                  load native agent library <libname>, e.g. -agentlib:jdwp
                  see also -agentlib:jdwp=help
    -agentpath:<pathname>[=<options>]
                  load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
                  load Java programming language agent, see java.lang.instrument
    -splash:<imagepath>
                  show splash screen with specified image
                  HiDPI scaled images are automatically supported and used
                  if available. The unscaled image filename, e.g. image.ext,
                  should always be passed as the argument to the -splash option.
                  The most appropriate scaled image provided will be picked up
                  automatically.
                  See the SplashScreen API documentation for more information
    @argument files
                  one or more argument files containing options
    -disable-@files
                  prevent further argument file expansion
    --enable-preview
                  allow classes to depend on preview features of this release
To specify an argument for a long option, you can use --<name>=<value> or
--<name> <value>.


C:\Users\genie.releng\workspace\AutomatedTests\ep427I-unit-win32-java17>exit 1 
Build step 'Execute Windows batch command' marked build as failure
Recording test results
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?
Archiving artifacts
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
Triggering a new build of Releng � Collect Results
Finished: FAILURE

Use github repositories to create source bundles

While publishing maven artifacts we need to publish source bundles as well. we may miss some source bundles. need to generate source bundles using the gir reposotories need to migrate the code to use github repos

No test results published on I20230317-1800

See https://download.eclipse.org/eclipse/downloads/drops4/I20230317-1800/.

Build succeeded, tests were executed, but the job that is supposed to publish test results failed.

See where the tests are executed - https://ci.eclipse.org/releng/job/AutomatedTests/ and
https://ci.eclipse.org/releng/job/Builds/job/I-build-4.28/20/console
I don't see any errors there.

However I see this job fails https://ci.eclipse.org/releng/job/Releng/job/ep-collectResults/, like https://ci.eclipse.org/releng/job/Releng/job/ep-collectResults/939/console

The error is hipp_shell: line 1: /opt/tools/java/openjdk/jdk-17/latest/bin/java: No such file or directory

No idea why it fails now. Was the path to Java 17 changed?

[19] Y builds are not running with Java 19

https://download.eclipse.org/eclipse/downloads/drops4/Y20220728-1000/testResults.php
Y builds should run with Java 19 also.

@sravanlakkimsetti

Maven export generates wrong dependencies (com.sun.jna instead of net.dev.java.jna)

Exported bundles on Maven Central have wrong dependencies.

For example the bundle org.eclipse.urischeme:jar:1.1.100 a dependency to
com.sun.jna:jar:[4.5.1,6.0.0) that does not exist on Maven Central.

The POM can be found at:
https://search.maven.org/remotecontent?filepath=org/eclipse/platform/org.eclipse.urischeme/1.1.0/org.eclipse.urischeme-1.1.0.pom

The following error happens when buildung a project with Maven:

Failed to collect dependencies at org.eclipse.platform:org.eclipse.ui.workbench:jar:3.116.0 -> 
org.eclipse.platform:org.eclipse.e4.ui.workbench.addons.swt:jar:1.2.100 -> 
org.eclipse.platform:org.eclipse.e4.ui.workbench.renderers.swt:jar:0.14.0 -> 
org.eclipse.platform:org.eclipse.e4.ui.workbench.swt:jar:0.14.1000 -> org.eclipse.platform:org.eclipse.urischeme:jar:1.1.100 -> 
com.sun.jna:com.sun.jna:jar:[4.5.1,6.0.0)

Another source of the problem is that the exported Maven POMs use version ranges for dependencies instead of fixed versions.
This regularly leads to broken builds if a newer version of some bundle is available on Maven Central. The generated POMs must use FIXED versions for dependencies.

Improve and simplify the stale information in the publish-to-maven-central

The following things should be revisited and cleaned up:

ArtifactInfo.SCM_GITROOT and ArtifactInfo.SCM_CGIT use git.eclipse.org so these can no longer be relevant.
ArtifactInfo.FRONT_MATTER references bugs.eclipse.org so that is no longer correct.
ArtifactInfo.COPYRIGHT is out of date and I have no idea why GK Software is the 'primary' copyright holder.
ArtifactInfo.fixData() is not needed anymore, I believe.
ArtifactInfo.getProject() seems to suggest that ECF artifacts are being published, but I don't think that's the case.
ArtifactInfo.extractScmUrl(String) is probably a no-op now.
ArtifactInfo.extractProjectRepo(String) is unused
Developer appears to be mostly noise with no calls to eveloper.addIndividualDevelopers so no use of Developer.IndividualDeveloper

It seems to me the design of ArtifactInfo.toPomFragment() is rather fragile, relying string matching/finding. In EMF's enhancer (contributed by Karsten Thoms) it use org.apache.maven.model.Model:

https://git.eclipse.org/c/emf/org.eclipse.emf.git/tree/releng/org.eclipse.emf.releng/publish/pommod/src/main/java/pommod/POMEnhancer.java

I think that would be less fragile to use a model with respect to future potential changes in the CBI aggregator generating richer poms in the first place.

I wonder if there is a way to test this stuff locally? That would make it easier to make changes and check for correctness of those changes....

4.29 I-Build: I20230609-1800 - BUILD FAILED

See https://ci.eclipse.org/releng/job/Builds/job/I-build-4.29/7/console

addToComposite task from ant runner started IDE with Java 11 and as expected (most of the platform requires Java 17 meanwhile) this doesn't work.

I have no idea how that worked before during 4.28 time (or did something changed in build scripts in 4.29?), but now obviously this doesn't work anymore:

01:26:55  --2023-06-09 19:26:55--  https://download.eclipse.org/eclipse/relengScripts/cje-production/scripts/addToComposite.xml
01:26:55  Resolving download.eclipse.org (download.eclipse.org)... 198.41.30.199
01:26:55  Connecting to download.eclipse.org (download.eclipse.org)|198.41.30.199|:443... connected.
01:26:55  HTTP request sent, awaiting response... 200 OK
01:26:55  Length: 816 [text/xml]
01:26:55  Saving to: ‘/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/addToComposite.xml’
01:26:55  
01:26:55       0K                                                       100%  459M=0s
01:26:55  
01:26:55  2023-06-09 19:26:55 (459 MB/s) - ‘/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/addToComposite.xml’ saved [816/816]
01:26:55  
01:26:58  Install location:
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/
01:26:58  Configuration file:
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/configuration/config.ini loaded
01:26:58  Configuration location:
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/configuration/
01:26:58  Framework located:
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/plugins/org.eclipse.osgi_3.18.400.v20230509-2241.jar
01:26:58  Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.2.800.v20221116-1440.jar
01:26:58  	eclipse.properties not found
01:26:58  Framework classpath:
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/plugins/org.eclipse.osgi_3.18.400.v20230509-2241.jar
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/plugins/
01:26:58      file:/home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/eclipse/plugins/org.eclipse.osgi.compatibility.state_1.2.800.v20221116-1440.jar
01:26:59  Debug options:
01:26:59      file:/opt/public/hipp/homes/genie.releng/.options not found
01:27:00  Time to load bundles: 174
01:27:06  !SESSION 2023-06-09 19:26:58.413 -----------------------------------------------
01:27:06  eclipse.buildId=4.28.0.I20230605-0440
01:27:06  java.version=11.0.10
01:27:06  java.vendor=Oracle Corporation
01:27:06  BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en
01:27:06  Framework arguments:  -application org.eclipse.ant.core.antRunner -file /home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/addToComposite.xml addToComposite -Drepodir=/home/data/httpd/download.eclipse.org/eclipse/updates/4.29-I-builds -Dcomplocation=I20230609-1800
01:27:06  Command-line arguments:  -consolelog -debug -data /home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/workspace-antRunner -application org.eclipse.ant.core.antRunner -file /home/data/httpd/download.eclipse.org/eclipse/workingDir/Builds/I-build-4.29-7/addToComposite.xml addToComposite -Drepodir=/home/data/httpd/download.eclipse.org/eclipse/updates/4.29-I-builds -Dcomplocation=I20230609-1800
01:27:06  
01:27:06  !ENTRY org.eclipse.ant.core 4 0 2023-06-09 19:27:06.629
01:27:06  !MESSAGE FrameworkEvent ERROR
01:27:06  !STACK 0
01:27:06  org.osgi.framework.BundleException: Could not resolve module: org.eclipse.ant.core [39]
01:27:06    Unresolved requirement: Require-Bundle: org.eclipse.core.variables; bundle-version="[3.1.0,4.0.0)"
01:27:06      -> Bundle-SymbolicName: org.eclipse.core.variables; bundle-version="3.6.0.v20230317-0802"; singleton:="true"
01:27:06         org.eclipse.core.variables [58]
01:27:06           Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"
01:27:06           Unresolved requirement: Require-Bundle: org.eclipse.core.runtime; bundle-version="[3.3.0,4.0.0)"
01:27:06             -> Bundle-SymbolicName: org.eclipse.core.runtime; bundle-version="3.27.0.v20230515-1719"; singleton:="true"
01:27:06                org.eclipse.core.runtime [57]
01:27:06                  Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"
01:27:06                  Unresolved requirement: Require-Bundle: org.eclipse.core.jobs; bundle-version="[3.13.0,4.0.0)"; visibility:="reexport"
01:27:06                    -> Bundle-SymbolicName: org.eclipse.core.jobs; bundle-version="3.14.0.v20230317-0901"; singleton:="true"
01:27:06                       org.eclipse.core.jobs [53]
01:27:06                         Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"
01:27:06                  Unresolved requirement: Require-Bundle: org.eclipse.core.contenttype; bundle-version="[3.8.0,4.0.0)"; visibility:="reexport"
01:27:06                    -> Bundle-SymbolicName: org.eclipse.core.contenttype; bundle-version="3.9.0.v20230412-0829"; singleton:="true"
01:27:06                       org.eclipse.core.contenttype [43]
01:27:06                         Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=17))"
01:27:06    Unresolved requirement: Require-Bundle: org.eclipse.core.runtime; bundle-version="[3.25.0,4.0.0)"
01:27:06      -> Bundle-SymbolicName: org.eclipse.core.runtime; bundle-version="3.27.0.v20230515-1719"; singleton:="true"
01:27:06  
01:27:06  	at org.eclipse.osgi.container.Module.start(Module.java:463)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
01:27:06  	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1786)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
01:27:06  	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
01:27:06  	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
01:27:06  	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

...,
tons of similar errors after and finally

01:27:08  !ENTRY org.eclipse.osgi 4 0 2023-06-09 19:27:08.549
01:27:08  !MESSAGE Application error
01:27:08  !STACK 1
01:27:08  java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
01:27:08  	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
01:27:08  	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)
01:27:08  	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
01:27:08  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
01:27:08  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
01:27:08  	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
01:27:08  	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
01:27:08  	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
01:27:08  	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
01:27:08  	at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
01:27:08  	at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
[Pipeline] }
01:27:09  Executing sh script inside container jnlp of pod aggrbuild-pod-n7t9c-6hwb0
01:27:09  Executing command: "ssh-agent" "-k" 
01:27:09  exit
01:27:09  unset SSH_AUTH_SOCK;
01:27:09  unset SSH_AGENT_PID;
01:27:09  echo Agent pid 24141 killed;
01:27:09  [ssh-agent] Stopped.
[Pipeline] // sshagent
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Trigger tests)
Stage "Trigger tests" skipped due to earlier failure(s)

Readme file for 4.28

Readme file needs to be added for 4.28.

For more details on the readme see Bug 493368.

ReadMe for 4.27 - #908

[PublishToMaven] Replace baseline file by checking the target Maven repository

At the moment, the decision whether to push a new version of one artifact or not is made via a baseline.txt file which is shared across multiple jobs on CI. This is rather fragile and we should probably target something more robust and simpler.
I suspect mvn deploy actually has it built-in: if we try to push an artifact that already exists with the same content in target repo, it may just skip is case file is not changed; or Nexus will fail in case a release was already made with the same version. In such case, we may remove this explicit checks for baseline and rely on Maven to work well.
If Maven isn't smart enough,then we should replace the baseline by retrieving repo metadata and checking whether artifact already existis for the same GAV+checksum. If yes, skip; if not; deploy.

No Windows tests since I20220620-1050

Haven't checked why, but Windows tests aren't running since I20220620-1050.
See https://download.eclipse.org/eclipse/downloads/

Fix dependency/groupId computation when publishing to Maven

In 4.24, some artifacts are now consumed directly from Maven and already have groupId/artifactId to be used when describing them as dependencies when generating pom files to publish to Maven Central.
The current https://github.com/eclipse-platform/eclipse.platform.releng/blob/master/publish-to-maven-central/SDK4Mvn.aggr defines static mapping rules that used to be reliable in the time of Orbit, but aren't any more. See eclipse-equinox/equinox.bundles#54 / eclipse-equinox/equinox.framework#70 for an instance of this problem.
The pom generator should be fixed to use the reference groupId/artifactId when listing dependencies as much as possible instead of hardcoding rules.

Enable discussions?

@akurtakov do you mind enabling discussions for this repository? I think it would be good for general releng questions/discussions.

sourceTemplateFeature and sourceTemplateFragment still needed?

Some of our features still have sourceTemplateFragment and sourceTemplateFeature folder included. Are these still used / necessary?

New features generated by the PDE wizard do not have these folders.

cc @HannesWell @sravanlakkimsetti @laeubi

bogus maven metadata in newly published maven artifacts for org.eclipse.equinox.preference

https://search.maven.org/artifact/org.eclipse.platform/org.eclipse.equinox.preferences/3.10.0/jar

has

    <dependency>
      <groupId>org.osgi.service</groupId>
      <artifactId>org.osgi.service.prefs</artifactId>
      <version>[1.1.0,1.2.0)</version>
    </dependency>

which does not exist
as the group id is org.osgi

https://search.maven.org/artifact/org.osgi/org.osgi.service.prefs/1.1.2/jar

The published pom for org.eclipse.osgi.util 3.7.0 on maven central is wrong

Since the original issue eclipse-equinox/equinox.bundles#54 has too many comments, I decided to open a new one.

org.eclipse.platform:org.eclipse.equinox.preferences:3.10.0 is not the only broken pom (see org.eclipse.equinox.preferences-3.10.0.pom on maven central).

There is also:
org.eclipse.platform:org.eclipse.osgi.util:3.7.0. See: org.eclipse.osgi.util-3.7.0.pom

The groupId org.osgi.util does not exist and should be org.osgi.

This is already fixed by #48 there is a new mapping:

eclipse.platform.releng/publish-to-maven-central/SDK4Mvn.aggr

Line 70 in 06dad07

Probably not so many people are impacted (because it does not seems to be a transitive dependency of jdt.core), but it would be healthy to published a fixed pom for this artifact as well.

Bad metadata published for org.eclipse.core.contenttype

Maven complains that org.eclipse.core.contenttype cannot satisfy its version range

No versions are present in the repository for the artifact with a range [3.2.0,4.0.0)

I think the problem is that the lowest available version is 3.6.1 here:

https://mvnrepository.com/artifact/org.eclipse.platform/org.eclipse.equinox.preferences

Please use proper version ranges when generating poms to be deployed to maven central

As already noticed in the recent IP issue, Platform currently produces (from maven point of view) very bad meta-data by using way to open version ranges. This can easily break consumers of such artifacts and threaten the stability of builds!

One example is:
https://mvnrepository.com/artifact/org.eclipse.platform/org.eclipse.equinox.p2.repository/2.6.200 which even use completely open ranges. That means maven will always resolve to the latest version on central, what obviously will only be a matter of time to break consumers.

This already broke Tycho here:

https://ci.eclipse.org/tycho/job/tycho-github/job/master/628/console

and even on a frozen branch here:

https://ci.eclipse.org/tycho/job/tycho-github/job/PR-1434/1/console

because the mentioned artifact now pulls in https://repo1.maven.org/maven2/org/bouncycastle/bcpg-jdk18on/1.72/ that was just release a few hours ago, while it was as far as I know compiled against https://mvnrepository.com/artifact/org.bouncycastle/bcpg-jdk18on/1.71

So if it is not know that a certain dependency can work (and compile!) with a range of version, the version used to produce that artifact should be used instead, what still will allow maven to use never version but prefer the given one if no one requests to do so see:
https://cwiki.apache.org/confluence/display/MAVENOLD/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges

Deploy Maven SNAPSHOT artifacts

Currently p2->Maven translation and deployment only happens for releases. In order to facilitate testing and verification and early adoption, we should publish frequent snapshots.
Snapshots would probably have to land to repo.eclipse.org since I believe OSSRH doesn't allow snapshots.

Publish 4.23 artifacts to maven central

Security Best Practices

Hi,

As a member of the Security Team from the Eclipse Foundation, we used a tools Scorecard and StepSecurity to analyze this repo in order to push a pull request that cover some or all the following best practices below:

Apply least privilege principle to GITHUB_TOKEN
Add or fine tune the use of Dependabot
Pin actions to a full length commit SHA

As a result, You will see a PR coming from StepSecurity to help to implement those fixes above which will cover a list of points below identified detected:

Apply least privilege principle to GITHUB_TOKEN for files .github/workflows/updateRelease.yml
Add or fine tune the use of Dependabot

Please don’t hesitate and reach out if there is something unclear above.

Kind Regards,
Francisco Perez

Unsatisfied constraint: 'Import-Package: com.ibm.icu.text; version="3.8.1"'

We see a severe issue with PDE/SDK in M1.

Bundles that import com.ibm.icu.text;version="3.8.1" package show PDE validation errors and also can't be activated on startup, if only com.ibm.icu bundle that is shipped with SDK is available in the platform.

This affects GEF and Webtools installed "offline" (not by using update sites connected to internet).

Example bundle with this MANIFESt.MF can't be started in pure SDK:

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: IcuTest
Bundle-SymbolicName: IcuTest;singleton:=true
Bundle-Version: 1.0.0.qualifier
Automatic-Module-Name: IcuTest
Bundle-RequiredExecutionEnvironment: JavaSE-11
Import-Package: com.ibm.icu.text;version="3.8.1"
Require-Bundle: org.eclipse.ui
Bundle-ActivationPolicy: lazy

!ENTRY IcuTest 4 0 2022-07-08 09:50:15.311
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: IcuTest [311]
  Unresolved requirement: Import-Package: com.ibm.icu.text; version="3.8.1"

	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

Generate pom files with actual versions for deps instead of ranges

Maven is not as good as p2 or OSGi with dependency ranges; moreover, unlike p2 repo where we can have a consistent subset of all possible artifacts that are known to work well together, a Maven repository such as Central is accumulative and keeps older versions or future ones just as accessible as whatever version the artifact was tested against.
Overall, usage of version ranges in Maven is unfortunately too risky for general usage; we should instead prefer publishing pom files specific artifact versions. This will make consumption via Maven work better in general, without preventing people from binding to different versions explicitly if they want/need to.

Preparations for publishing 4.26 to Maven

I wanted to plan ahead to record what I think needs attention to properly published the 4.26 release to Maven central...

The following file needs updating probably:

https://github.com/eclipse-platform/eclipse.platform.releng/blob/master/publish-to-maven-central/baseline.txt

But it wasn't updated for the 4.25 release:

This needs updating, but can't be updated until the release is available in the drops4 folder:

eclipse.platform.releng/publish-to-maven-central/properties.sh

Lines 15 to 22 in c9a0d76

 # ECLIPSE: 

 DROPS4=/home/data/httpd/download.eclipse.org/eclipse/downloads/drops4 

 SDK_BUILD_DIR=R-4.25-202208311800 

 SDK_VERSION=4.25 

 FILE_ECLIPSE=${DROPS4}/${SDK_BUILD_DIR}/eclipse-SDK-${SDK_VERSION}-linux-gtk-x86_64.tar.gz 

 # JDT / ECJ: 

 ECJ_VERSION=3.32.0

This always fails when we build the snapshot versions and should be fixed

eclipse.platform.releng/publish-to-maven-central/CBIaggregator.sh

Lines 388 to 389 in c9a0d76

	# copy ecj-src from build output (NB: we are mapping from SDK version (4.x) back to ECJ version (3.x)):
	scp [email protected]:${DROPS4}/${SDK_BUILD_DIR}/ecjsrc-${SDK_VERSION}.jar org/eclipse/jdt/ecj/${ECJ_VERSION}/ecj-${ECJ_VERSION}-sources.jar

This is likely a problem too:

eclipse.platform.releng/publish-to-maven-central/publishJDT.sh

Lines 119 to 128 in c9a0d76

 # WORKAROUND TO PUBLISH ECJ SOURCES AS REQUESTED BY NEXUS 

 # PRETTY FRAGILE! NEEDS VERSION UPDATES ON EVERY STREAM 

 # suggested fix: https://github.com/eclipse-jdt/eclipse.jdt.core/issues/384 

 wget https://download.eclipse.org/eclipse/downloads/drops4/R-4.25-202208311800/download.php?dropFile=ecjsrc-4.25.jar -o ecjsrc.jar 

 for pomFile in org/eclipse/jdt/ecj/*/ecj-*.pom; do 

 ${MVN} -f jdt-pom.xml -s ${SETTINGS} gpg:sign-and-deploy-file \ 

 -Durl=${URL} -DrepositoryId=${REPO} \ 

 -Dfile=ecjsrc.jar -DpomFile=${pomFile} -Dclassifier=sources \ 

 >> .log/sources-upload.txt 

 done

These three references to the 4.26-I-Builds probably need attention too because there appear to be 2 I-Build after the RC2 version:

eclipse.platform.releng/publish-to-maven-central/SDK4Mvn.aggr

Lines 4 to 20 in c9a0d76

 <contributions label="sdk"> 

 <repositories enabled="false" location="/home/data/httpd/download.eclipse.org/eclipse/updates/4.26-I-builds/"> 

 <mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.feature.group"/> 

 <mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.source.feature.group"/> 

 </repositories> 

 <repositories enabled="false" location="/home/data/httpd/download.eclipse.org/eclipse/updates/4.26-I-builds/"> 

 <bundles name="org.eclipse.jdt.core.compiler.batch"/> 

 </repositories> 

 </contributions> 

 <contributions label="sdk_http"> 

 <repositories location="https://download.eclipse.org/eclipse/updates/4.26-I-builds/"> 

 <mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.feature.group"/> 

 <mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.source.feature.group"/> 

 </repositories> 

 <repositories location="https://download.eclipse.org/eclipse/updates/4.26-I-builds/"> 

 <bundles name="org.eclipse.jdt.core.compiler.batch"/> 

 </repositories>

Publish Eclipse features to Maven Central

Hello everyone,

currently only the Eclipse plugin are published to Maven Central. I think it would be helpful to publish the features, as well.

Use Case:

In order to be FOSS compliant, we want to use Black Duck in combination with Tycho for our RCP application. However, the tool is only able to look at the project from a Maven perspective, meaning that it requires the artifacts to have proper Maven metadata, in order to be detected.

We currently retrieve the Eclipse artifacts via the corresponding p2 repositories and therefore, the tool simply ignores them. So I'm playing with the idea to instead, add them via Maven instead. Which requires a Maven counterpart for both plugins and features.

Is there a technical reason why features can't be published or wasn't there just any need for it so far?

.eclipseproduct has version=4.26.0 in 4.27 release

eclipse/.eclipseproduct in the Eclipse IDE 2023-03 R tarball for Linux x86_64 (and presumably other systems) contains version=4.26.0:

curl -LsS https://download.eclipse.org/technology/epp/downloads/release/2023-03/R/eclipse-java-2023-03-R-linux-gtk-x86_64.tar.gz | tar -xzO eclipse/.eclipseproduct

prints

name=Eclipse Platform
id=org.eclipse.platform
version=4.26.0

Presumably this is an oversight and it should be updated to version=4.27.0 in https://github.com/eclipse-platform/eclipse.platform.releng/blob/master/features/org.eclipse.platform-feature/rootfiles/.eclipseproduct?

Related issues from previous releases:

Bug 577718 - .eclipseproduct has version=4.21.0 in 4.22 release
Bug 567270 - .eclipseproduct still has 4.17
Bug 533757 - 4.8 SDK builds have 4.7.0 in .eclipseproduct file
Bug 407466 - Update .eclipseproduct file
Bug 378220 - .eclipseproduct file still defines version=version=3.7.0 for Eclipse 3.8
Bug 28325 - .eclipseproduct still has version 2.0.0
Bug 258360 - .eclipseproduct still says version 3.4.0
Bug 231394 - .eclipseproduct contains version=3.3.0
Bug 181725 - .eclipseproduct still says "3.2.0"
Bug 139997 - .eclipseproduct still has version 3.1.0

Automation was proposed in

Bug 476075 - Investigate if version in .eclipseproduct file can be automated

Thanks,
Kevin

https://download.eclipse.org/eclipse/updates/4.25-I-builds contains empty categories

We have three categories which are empty in our update site:

API Tools...
CVS Client
Releng Tools

Should we remove these categories? cc @vik-chand @akurtakov ?

Publish to maven central

Maven export should use fixed ranges

The issue is transferred from here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=578085

The deployment of org.eclipse.jdt:org.eclipse.jdt.core:XXXX on Maven uses version ranges to specify its dependencies e.g. org.eclipse.platform:org.eclipse.text:[3.6.0,4.0.0)

The problem with this is that it's too open ended and when trying to retrieve the last version that supported jdk8 (version 3.25.0), the transitive dependencies bring in versions that are compiled for jdk11 e.g. org.eclipse.platform:org.eclipse.text last jdk8 version was 3.9.0 but version 3.12.0 is chosen which compiles to jdk11 so can't be used.

I can see this being an issue in the future on the switch from jdk11 -> 17.

So would it be possible to change to using strict dependency version numbers in the pom.xml deployed to Maven instead of ranges. Currently to get the jdk8 version working I have to specify all the transitive dependencies manually.

All the transitive dependencies that bring in more dependencies also use ranges...
org.eclipse.jdt:org.eclipse.jdt.core
org.eclipse.platform:org.eclipse.ant.core
org.eclipse.platform:org.eclipse.compare.core
org.eclipse.platform:org.eclipse.core.commands
org.eclipse.platform:org.eclipse.core.contenttype
org.eclipse.platform:org.eclipse.core.expressions
org.eclipse.platform:org.eclipse.core.filesystem
org.eclipse.platform:org.eclipse.core.jobs
org.eclipse.platform:org.eclipse.core.resources
org.eclipse.platform:org.eclipse.core.runtime
org.eclipse.platform:org.eclipse.core.variables
org.eclipse.platform:org.eclipse.equinox.app
org.eclipse.platform:org.eclipse.equinox.common
org.eclipse.platform:org.eclipse.equinox.preferences
org.eclipse.platform:org.eclipse.equinox.registry
org.eclipse.platform:org.eclipse.osgi
org.eclipse.platform:org.eclipse.team.core
org.eclipse.platform:org.eclipse.text

Add an action to check PR's don't have merge commits

In 99% if cases in the platform (except "next" Java branch work in JDT) we won't have merge commits in PR's, to have a clean and easy to understand git history.

However, most of github contributors simply don't know that, don't care in general and so do whatever possible with git in their PR's. This causes frustration on both sides.

There is a way to "disable" merge commits in general in the repo, but sometimes it is needed, and it also doesn't check PR's commits, only on "merge" action.

I think better would be if PR validation fails automatically.

We should check if there is a Github Action available that can be configured for all platfrom repo and show an error on PR's with merge commits.

POM and product version change for 4.24 release

linked to eclipse-platform/eclipse.platform.releng.aggregator#58

Validate all poms are resolvable

Discussion started in #50 .
Goal is to have poms verified/validated to be resolvable by Maven independent of the way these poms are generated

tar files now generate warnings when extracting

When I extract eclipse-platform-4.26M3-linux-gtk-x86_64.tar.gz I get a bunch of warnings. I don't get these warnings with 4.25 nor 4.26 M2. As every file and folder generates this warning, with the SDK tar that means > 1000 warnings.

$ tar xf ~/Downloads/eclipse-platform-4.26M3-linux-gtk-x86_64.tar.gz 
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.creationtime'
...

$ tar --version
tar (GNU tar) 1.30
Copyright (C) 2017 Free Software Foundation, Inc.

I am on Ubuntu (Xubuntu specifically) 20.04.

Simrel contains multiple versions of org.eclipse.sdk.feature.group

Not sure if we intended to do this, but the simrel contains multiple versions of the Eclipse SDK feature.

Is this expected / desired? IIRC the simrel is very concerned about multiple versions.

@merks @jonahgraham FYI

Move into eclipse.platform.releng.aggregator?

I believe it would be simpler to have this content part of eclipse.platform.releng.aggregator directly. Should we move it?

Linux Java 17 build fails since I20230116-1800

See

Jan 17, 2023 12:34:06 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: Failed to connect to http://jenkins-ui.releng.svc.cluster.local/releng/tcpSlaveAgentListener/: jenkins-ui.releng.svc.cluster.local
java.io.IOException: Failed to connect to http://jenkins-ui.releng.svc.cluster.local/releng/tcpSlaveAgentListener/: jenkins-ui.releng.svc.cluster.local
	at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:214)
	at hudson.remoting.Engine.innerRun(Engine.java:745)
	at hudson.remoting.Engine.run(Engine.java:544)
Caused by: java.net.UnknownHostException: jenkins-ui.releng.svc.cluster.local
	at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:229)
	at java.base/java.net.Socket.connect(Socket.java:609)
	at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:177)
	at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:508)
	at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:603)
	at java.base/sun.net.www.http.HttpClient.<init>(HttpClient.java:276)
	at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:375)
	at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:396)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1253)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1187)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:1015)
	at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:211)
	... 2 more

Maven SNAPSHOT for Eclipse project can't resolve dependencies

$ mvn dependency:get -Dartifact=org.eclipse.platform:org.eclipse.ui.workbench:3.127.0-SNAPSHOT -DremoteRepositories=https://repo.eclipse.org/content/repositories/eclipse-snapshots/
[...]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  44.985 s
[INFO] Finished at: 2022-10-21T20:41:34+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:get (default-cli) on project payara-jdk-tester: Couldn't download artifact: Missing:
[ERROR] ----------
[ERROR] 1) org.eclipse.platform:org.eclipse.core.jobs:jar:3.13.200
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.core.jobs -Dversion=3.13.200 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.core.jobs -Dversion=3.13.200 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.core.jobs:jar:3.13.200
[ERROR] 
[ERROR] 2) org.eclipse.platform:org.eclipse.equinox.common:jar:3.17.0
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.equinox.common -Dversion=3.17.0 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.equinox.common -Dversion=3.17.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.core.runtime:jar:3.26.0
[ERROR]   	4) org.eclipse.platform:org.eclipse.equinox.common:jar:3.17.0
[ERROR] 
[ERROR] 3) org.eclipse.platform:org.eclipse.osgi:jar:3.18.200
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.osgi -Dversion=3.18.200 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.osgi -Dversion=3.18.200 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.core.runtime:jar:3.26.0
[ERROR]   	4) org.eclipse.platform:org.eclipse.osgi:jar:3.18.200
[ERROR] 
[ERROR] 4) org.eclipse.platform:org.eclipse.jface:jar:3.28.0
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.jface -Dversion=3.28.0 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.jface -Dversion=3.28.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.jface:jar:3.28.0
[ERROR] 
[ERROR] 5) org.eclipse.platform:org.eclipse.swt:jar:3.121.100
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.swt -Dversion=3.121.100 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.swt -Dversion=3.121.100 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.swt:jar:3.121.100
[ERROR] 
[ERROR] 6) org.eclipse.platform:org.eclipse.jface.databinding:jar:1.14.0
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.jface.databinding -Dversion=1.14.0 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.jface.databinding -Dversion=1.14.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.jface.databinding:jar:1.14.0
[ERROR] 
[ERROR] 7) org.eclipse.platform:org.eclipse.e4.core.services:jar:2.3.400
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.core.services -Dversion=2.3.400 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.core.services -Dversion=2.3.400 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.core.services:jar:2.3.400
[ERROR] 
[ERROR] 8) org.eclipse.platform:org.eclipse.e4.ui.workbench.swt:jar:0.16.700
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.swt -Dversion=0.16.700 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.swt -Dversion=0.16.700 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.ui.workbench.swt:jar:0.16.700
[ERROR] 
[ERROR] 9) org.eclipse.platform:org.eclipse.e4.ui.css.swt.theme:jar:0.13.200
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.css.swt.theme -Dversion=0.13.200 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.css.swt.theme -Dversion=0.13.200 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.ui.css.swt.theme:jar:0.13.200
[ERROR] 
[ERROR] 10) org.eclipse.platform:org.eclipse.e4.ui.css.swt:jar:0.14.700
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.css.swt -Dversion=0.14.700 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.css.swt -Dversion=0.14.700 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.ui.css.swt:jar:0.14.700
[ERROR] 
[ERROR] 11) org.eclipse.platform:org.eclipse.e4.ui.workbench.addons.swt:jar:1.4.500
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.addons.swt -Dversion=1.4.500 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.addons.swt -Dversion=1.4.500 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.ui.workbench.addons.swt:jar:1.4.500
[ERROR] 
[ERROR] 12) org.eclipse.platform:org.eclipse.e4.ui.workbench.renderers.swt:jar:0.15.700
[ERROR] 
[ERROR]   Try downloading the file manually from the project website.
[ERROR] 
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.renderers.swt -Dversion=0.15.700 -Dpackaging=jar -Dfile=/path/to/file
[ERROR] 
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=org.eclipse.platform -DartifactId=org.eclipse.e4.ui.workbench.renderers.swt -Dversion=0.15.700 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR] 
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) org.eclipse.platform:org.eclipse.ui.workbench:jar:3.127.0-SNAPSHOT
[ERROR]   	3) org.eclipse.platform:org.eclipse.e4.ui.workbench.renderers.swt:jar:0.15.700
[ERROR] 
[ERROR] ----------
[ERROR] 12 required artifacts are missing.
[ERROR] 
[ERROR] for artifact: 
[ERROR]   org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR] 
[ERROR] from the specified remote repositories:
[ERROR]   central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false),
[ERROR]   temp (https://repo.eclipse.org/content/repositories/eclipse-snapshots/, releases=true, snapshots=true)

The reason since to be that since we've replaced the dependency version ranges with actual dependencies, the -SNAPSHOT are not added to other artifacts coming from the same "reactor".

DNF in most Linux test suites with I20230314-1800

See https://download.eclipse.org/eclipse/downloads/drops4/I20230314-1800/testResults.php

Common thing seem to be some low level SWT issue:

!ENTRY org.eclipse.jface 2 0 2023-03-15 00:23:12.170
!MESSAGE The image could not be loaded: URLImageDescriptor(platform:/plugin/org.eclipse.e4.ui.workbench.renderers.swt/icons/full/ovr16/pinned_ovr.png)
!STACK 0
org.eclipse.jface.resource.DeviceResourceException: Unable to create resource URLImageDescriptor(platform:/plugin/org.eclipse.e4.ui.workbench.renderers.swt/icons/full/ovr16/pinned_ovr.png)
	at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:232)
	at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:55)
	at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:88)
	at org.eclipse.jface.resource.LazyResourceManager.create(LazyResourceManager.java:103)
	at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:195)
	at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:206)
	at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.getImageFromURI(SWTPartRenderer.java:228)
	at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.init(SWTPartRenderer.java:326)
	at org.eclipse.e4.ui.workbench.renderers.swt.WorkbenchRendererFactory.initRenderer(WorkbenchRendererFactory.java:145)
	at org.eclipse.e4.ui.workbench.renderers.swt.WorkbenchRendererFactory.getRenderer(WorkbenchRendererFactory.java:135)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.getRenderer(PartRenderingEngine.java:1024)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:991)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:659)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:763)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:728)

I don't see breaking changes in SWT or platform UI itself, so probably related to the new container build, see

Don't lock in a specific version of Lucene in the help feature

The help feature includes Lucene bundles.

eclipse.platform.releng/features/org.eclipse.help-feature/feature.xml

Lines 59 to 79 in acb9634

 <plugin 

 id="org.apache.lucene.analysis-common" 

 download-size="0" 

 install-size="0" 

 version="0.0.0" 

 unpack="false"/> 

 <plugin 

 id="org.apache.lucene.core" 

 download-size="0" 

 install-size="0" 

 version="0.0.0" 

 unpack="false"/> 

 <plugin 

 id="org.apache.lucene.analysis-smartcn" 

 download-size="0" 

 install-size="0" 

 version="0.0.0" 

 unpack="false"/>

This locks in a very specific version. The only bundle that actually requires Lucene allows a range of versions:

Does anything speak against removing the includes?

	# ECLIPSE:
	DROPS4=/home/data/httpd/download.eclipse.org/eclipse/downloads/drops4
	SDK_BUILD_DIR=R-4.25-202208311800
	SDK_VERSION=4.25
	FILE_ECLIPSE=${DROPS4}/${SDK_BUILD_DIR}/eclipse-SDK-${SDK_VERSION}-linux-gtk-x86_64.tar.gz

	# JDT / ECJ:
	ECJ_VERSION=3.32.0

	# WORKAROUND TO PUBLISH ECJ SOURCES AS REQUESTED BY NEXUS
	# PRETTY FRAGILE! NEEDS VERSION UPDATES ON EVERY STREAM
	# suggested fix: https://github.com/eclipse-jdt/eclipse.jdt.core/issues/384
	wget https://download.eclipse.org/eclipse/downloads/drops4/R-4.25-202208311800/download.php?dropFile=ecjsrc-4.25.jar -o ecjsrc.jar
	for pomFile in org/eclipse/jdt/ecj//ecj-.pom; do
	${MVN} -f jdt-pom.xml -s ${SETTINGS} gpg:sign-and-deploy-file \
	-Durl=${URL} -DrepositoryId=${REPO} \
	-Dfile=ecjsrc.jar -DpomFile=${pomFile} -Dclassifier=sources \
	>> .log/sources-upload.txt
	done

	<contributions label="sdk">
	<repositories enabled="false" location="/home/data/httpd/download.eclipse.org/eclipse/updates/4.26-I-builds/">
	<mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.feature.group"/>
	<mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.source.feature.group"/>
	</repositories>
	<repositories enabled="false" location="/home/data/httpd/download.eclipse.org/eclipse/updates/4.26-I-builds/">
	<bundles name="org.eclipse.jdt.core.compiler.batch"/>
	</repositories>
	</contributions>
	<contributions label="sdk_http">
	<repositories location="https://download.eclipse.org/eclipse/updates/4.26-I-builds/">
	<mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.feature.group"/>
	<mapRules xsi:type="aggregator:ExclusionRule" name="org.eclipse.e4.core.tools.feature.source.feature.group"/>
	</repositories>
	<repositories location="https://download.eclipse.org/eclipse/updates/4.26-I-builds/">
	<bundles name="org.eclipse.jdt.core.compiler.batch"/>
	</repositories>

	<plugin
	id="org.apache.lucene.analysis-common"
	download-size="0"
	install-size="0"
	version="0.0.0"
	unpack="false"/>

	<plugin
	id="org.apache.lucene.core"
	download-size="0"
	install-size="0"
	version="0.0.0"
	unpack="false"/>

	<plugin
	id="org.apache.lucene.analysis-smartcn"
	download-size="0"
	install-size="0"
	version="0.0.0"
	unpack="false"/>

eclipse-platform / eclipse.platform.releng Goto Github PK

eclipse.platform.releng's People

Contributors

Stargazers

Watchers

Forkers

eclipse.platform.releng's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs