[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500733#comment-17500733 ] Karl Pauls commented on SLING-9624: --- right, but the versions are the versions sling had since a long time. I don't know why they where like they where. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > Time Spent: 10m > Remaining Estimate: 0h > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500714#comment-17500714
]
Konrad Windszus commented on SLING-9624:
I am confused by the exported version of the javax.xml packages. This is what I
found out:
||Spec||Version||Link||
|JavaTM API for XML Processing (JAXP)|1.6 (since Java
8)|https://www.jcp.org/en/jsr/detail?id=206|
|Streaming API for XML (Stax)|1.3|https://jcp.org/en/jsr/detail?id=173|
|J2METM Web Services Specification|1.1|https://jcp.org/en/jsr/detail?id=172|
|XML API for JavaTM ME|1.0|https://jcp.org/en/jsr/detail?id=280|
|XML Catalogs|Version 1.1 (only
Java9+)|https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html|
But for example package {{javax.xml.namespace}} is exported as 2.1.0 although
it implements JAXP 1.3...
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500713#comment-17500713 ] Karl Pauls commented on SLING-9624: --- Right, that was the issue - we had bundles that have imports with version ranges that assume the old package versioning sling did. Thats why I did massage the exports of the system bundle to work with that and still pick up the modules from the jvm where possible. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500702#comment-17500702
]
Konrad Windszus commented on SLING-9624:
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. JAXP 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447523#comment-17447523 ] Konrad Windszus commented on SLING-9624: Now it is in https://github.com/apache/sling-org-apache-sling-starter/blob/812bc61cd81c6e21f14c05c89ce1e5ec91a353b4/src/main/features/boot.json#L147 > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 12 > > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
