Multiple versions of Jetty bundles cause Missing Constraint problems

[andrew-tram]

Jetty Version

Jetty 10.0.20 and 12.0.6

Jetty Environment

Probably not applicable.

Java Version

Java 21

Question

Is it expected that having multiple versions of Jetty plugins will cause Missing Constraint problems? I need to have both versions to satisfy dependencies. EGit seems to require Jetty 10.x and in-house, Eclipse 4.31, and WTP 3.33 plugins need Jetty 12.x

With everything selected:

With just 12.x selected:

With just 10.x selected:

[joakime]

Sounds like a question for the OSGi folks.

Your "With just 12.x selected:" and "With just 10.x selected:" screenshots contain both 10 and 12 versions.

Also, as a reminder, Jetty 10 is now at End of Community Support.

• End of Community Support for Jetty 10 / Jetty 11 - January 2024 #10485

You should be using Jetty 12 only at this point in time.

I also let jgit know ...

• Jetty 10 is at End of Community Support - upgrade to Jetty 12 eclipse-jgit/jgit#41

[andrew-tram]

My selection toggling was only between bundles that have two versions. Bundles that only have 12 seem to be fine

[janbartel]

You should be able to deploy multiple versions of jetty in the same OSGi container and have them resolve correctly by version. Whatever environment you're using seems to be resolving by bundle name - note that the validation errors are headlined by bundle name without the version. Can you get any more debug out of that tool?

[andrew-tram]

@janbartel , I'm using my own products as the target platform for launching and debugging. From a build and packaging standpoint, it seems fine. But that warning shows up when trying to launch a debug instance from itself. Toggling the different versions displays different errors which makes it seems like only one major version can be included at one time.

[janbartel]

@andrew-tram without more info to see the full resolution problems, I can't offer you any further advice, other than something isn't resolving against a correct version. Whether that is one of the eclipse bundles you're using, your own bundles, or jetty itself is impossible to tell from the info on this issue.

[andrew-tram]

@janbartel ,

I think this should be a valid example to demonstrate this...

• Download Eclipse IDE for RCP and RAP Developers 2024-03, which should have Jetty 12 content in there
• Launch, then try to install Jetty 10 content from this repo - https://download.eclipse.org/oomph/jetty/release/10.0.20
• Select just one feature like Jetty::Server Core to speed up any dependency resolution
• It won't allow the install since Jetty server 12 is already part of the platform

"Jetty :: Server Core" will be ignored because a newer version is already installed.

I checked, and org.eclipse.jetty.server is not a singleton, therefore should install? But something is preventing it.