what does: Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.1))" that exactly mean? #1084
-
|
Hi, this is not directly related to tycho, but i know there are a lot that knows a lot about this stuff here (and i don't know where i should exactly report this for eclipse) The new eclipse (i think WebTools.. not sure) has suddenly upgraded the apache xml resolver but now with the latest eclipse if you download for example it is: org.apache.xml.resolver_1.2.0.v20220401-1849.jar there are quite some changes in the manifest for that, including: Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.1))" if i read that correctly, does that say that it requires java 1.1 ?? because now if i have my target platform all to the new 4.24/2022.06 and i validate my launch config..
(my execution environment is java 17) so is this a bug now in the new manifest? they entered something wrong there, or does the validate of the launch target report this wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
Yes see http://docs.osgi.org/reference/eenames.html JavaSE-1.1 is not a valid EE
Don't know if it is useful these days, but if it really want to target Java 1.1, the lowest java version official supported is |
Beta Was this translation helpful? Give feedback.
-
|
J2SE-1.2 is for the BREE but for osgi.ee capability it has to be JavaSE . It's another question whether JavaSE-1.1 is supported version based on the the fact that 1.1 is not supposed for BREE, it shouldn't be supported for osgi.ee capability. |
Beta Was this translation helpful? Give feedback.
-
Do you have a link at hand for this?
1.2 is the lowest java version an OSGi framework can run on, so it really makes no sense to declare 1.1 as you never could run such a bundle on java 1.1 :-) |
Beta Was this translation helpful? Give feedback.
-
Sure, it's your own link http://docs.osgi.org/reference/eenames.html#osgiee-capability . There is no J2SE valid value for osgi.ee . Note how BREE: J2SE-1.5 but osgi.ee JavaSE-1.5 . |
Beta Was this translation helpful? Give feedback.
-
|
Thanks I must have missed that 👍 |
Beta Was this translation helpful? Give feedback.
-
|
It's definetely not a Tycho problem. I strongly recommend people to stop using Orbit artifacts or to work on Orbit so it stops overwriting original authors OSGi manifests. I replied to the PDE issue on the topic here eclipse-pde/eclipse.pde#179 (comment) . See the discussion there - there are more than 1 issue in different places and different projects/plugins but Java 1.1 is not smth worth spending time on. |
Beta Was this translation helpful? Give feedback.
-
|
yeah i found it... the supported list of profiles is in the OSGI plugin:
so yes as far as i read if you want to target 1.1 they should have taken JRE-1.1 not JavaSE-1.1 I have to say for some jars we also do it, but we then just fork it.. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, valid entries are specified in https://github.com/eclipse-equinox/equinox/blob/master/bundles/org.eclipse.osgi/JRE-1.1.profile#L21: Best is to report to/fix in Orbit so it doesn't put invalid osgi.ee requirements . |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Not sure if it's a valid workaround for you, but I have just added the old version of xml.resolver to our target (and use it explicitly in launch configs) and have not run into trouble until now. |
Beta Was this translation helpful? Give feedback.
yeah i found it...
the supported list of profiles is in the OSGI plugin:
so yes as far as i read if you want to target 1.1 they should have taken JRE-1.1 not JavaSE-1.1
I have to say for some jars we also do it, but we then just fork it..
Because if the original developers don't care about osgi then it is very tricky, i need to "osgify" the jar..
I guess thats why on maven we have for some jars so many different releases over different groups...