Karl Pauls
Karl Pauls
The problem with the bundle classpath is that it needs to be conditional. So you would need an entry for each existing java version.
> No. There will be multiple fragments which only resolve for the specific java version. But they need to override each other.
> No. At most one of the fragments is attached and it supplies classes in the versioned folder. So you would duplicate all classes from the other versions that are...
the thing is you can have: /A.class /9/B.class /10/C.class /11/B.class
> Why would you need to do that? Does multi release jars stack up all the versions? So that on Java 11, you search 11, then 10, then 9, then...
At least that is what I think http://openjdk.java.net/jeps/238 is saying
> In the example above, when running on an MRJAR-aware Java 9 JDK, it would see the 9-specific versions of A and B and the general versions of C and...
Part of me wonders if the solution is to really make them fragments inside the bundle. I.e., if a dir on the bundle-classpath has a META-INF/MANIFEST.mf we should just handle...
> A smaller problem is that the fragment for Java 9 would resolve on Java 10 because EEs include every previous EE. We would have to express a dependency on...
Bundle-Classpath: META-INF/versions/10,META-INF/versions/9,. and then what you just proposed as layout.