Skip to content

Conversation

@chrisrueger
Copy link
Contributor

Experimental branch for Eclipse 4.35 2025-03 ( corresponding to #6536 which is for Eclipse 4.34 2024-12)

instead of handcrafted at https://bndtools.jfrog.io/bndtools/bnd-build/eclipse/4.25/index.xml.gz

This could make it easier to test and use newer Eclipse Versions, since we start having more and more bugs only happening in newer Eclipse versions.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
note: version difference is on purpose (the asm:9.2 and the rest of asm.* 9.3). 9.2 is required by org.parboiled:parboiled-java:1.4.1 )

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
which is smaller, but requires a few other repositories (emf,jgit,m2e,wst) to be able to resolve the .bndrun files

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Still some startup issues m2e, but bndtools starts
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Note: for windows and linux I had to remove some requirements, since I guess the bundles do not exist anymore. I noticed via Repository Explorer they are disappearing around 2024-03

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

upgrade to Eclipse 4.35 (2025-03)

- resolve all .bndruns
- fixed some compilation problems because of stuff which was removed from Eclipse 4.35

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
@chrisrueger chrisrueger changed the title Upgrade to eclipse 4.35 2025 03 Upgrade to Eclipse 4.35 2025 03 Apr 1, 2025
@chrisrueger chrisrueger changed the title Upgrade to Eclipse 4.35 2025 03 Upgrade to Eclipse 4.35 2025-03 Apr 1, 2025
@chrisrueger chrisrueger changed the title Upgrade to Eclipse 4.35 2025-03 WIP Upgrade to Eclipse 4.35 2025-03 Apr 1, 2025
it took me hours to find the reason for the error which was that the BSN changed from org.slf4j.api (in slf4j 1.7.3 which was part of Eclipse 4.25) to slf4j.api ( slf4j 1.7.25 which is in central.maven but not part of eclipse 4.34 anymore)

java.lang.IllegalArgumentException
        at org.eclipse.equinox.internal.provisional.p2.core.VersionParser.parseInto(VersionParser.java:71)

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
TODO still getting build errors  (Task :bndtools.core.test:testOSGi FAILED)

bndtools.core.test.editors.quickfix.BuildpathQuickFixProcessor_WithEmptyBuildpath_Test <<< ERROR: Cannot invoke "org.osgi.framework.BundleContext.getBundles()" because "bc" is null

May related to the jupiter and junit versions which I downgraded to make it resolve. May have to adjust again.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
because Eclipse 4.34 requires Java 21 minimum

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
this finally fixed bndtools.core.test for me.
resolved all test .bndruns again

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
hopefully fixes build / test errors like java.lang.NoClassDefFoundError: org/bouncycastle/asn1/misc/MiscObjectIdentifiers

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
try to fix  Exception java.lang.NoClassDefFoundError: org/bouncycastle/asn1/misc/MiscObjectIdentifiers in biz.aQute.bndlib.comm.tests:test

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
to fix HttpTestServerTest

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
- resolve all .bndruns
- fixed some compilation problems because of stuff which was removed from Eclipse 4.35

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>
@chrisrueger chrisrueger force-pushed the upgrade-to-eclipse-4.35-2025-03 branch from b52bf27 to 752a5e4 Compare April 2, 2025 15:44
@chrisrueger
Copy link
Contributor Author

chrisrueger commented Apr 2, 2025

Current status:

  • I can launch bndtools Eclipse instance based on Eclipse 4.35 2025-03
  • Test fails
image

I develop this PR re-based on #6536 (for Eclipse 4.34 2024-12) to find out where the problems are between the two versions.

@chrisrueger
Copy link
Contributor Author

Closing and retrying after #7000 which should solve the JUnit problems. But we will start over fresh and just use this as a template.

@chrisrueger chrisrueger closed this Jan 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant