You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/02/13 11:04:13 UTC

[jira] [Resolved] (SLING-2720) Update exported versions for extension fragments to match well-known JAX-WS, JAXB, StAX and JAF versions

     [ https://issues.apache.org/jira/browse/SLING-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2720.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: Framework Extension Fragment WS 1.0.2
                   Framework Extension Fragment XML 1.0.2
                   Framework Extension Fragment Activation 1.0.2

Thanks for your patch, lgtm - applied
                
> Update exported versions for extension fragments to match well-known JAX-WS, JAXB, StAX and JAF versions
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-2720
>                 URL: https://issues.apache.org/jira/browse/SLING-2720
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Framework Extension Fragment WS 1.0.0, Framework Extension Fragment XML 1.0.0, Framework Extension Fragment Activation 1.0.0
>            Reporter: Robert Munteanu
>            Assignee: Carsten Ziegeler
>             Fix For: Framework Extension Fragment Activation 1.0.2, Framework Extension Fragment XML 1.0.2, Framework Extension Fragment WS 1.0.2
>
>         Attachments: SLING-2720-1.patch, SLING-2720.patch
>
>
> The framework extension packages currently export their packages versioned as 0.0.0_fragment_qualifier. However, some third-party OSGi bundles, notably CXF [1] require specific versions. One example is Jax-WS 2.1.0 or newer.
> To fix this, I propose that we export the packages with well-known package versions for versions which are easily identifiable. The versions are proposed based on specific documentation outlining the inclusion of these frameworks in Java 6 [2], [3] . Also, based on a bug report[4] I have inferred that the StAX version available in Java 6 ( FCS, later updates have newer packages ) is 1.0.0.
> - JAX-WS 2.1, packages
> javax.xml.ws
> javax.xml.ws.handler
> javax.xml.ws.handler.soap
> javax.xml.ws.http
> javax.xml.ws.soap
> javax.xml.ws.spi
> javax.xml.ws.spi.http
> javax.xml.ws.wsaddressing
> - JAXB 2.1 packages
> javax.xml.bind
> javax.xml.bind.annotation
> javax.xml.bind.annotation.adapters
> javax.xml.bind.attachment
> javax.xml.bind.helpers
> javax.xml.bind.util
> javax.xml.datatype
> - STAX 1.0 packages
> javax.xml.stream
> javax.xml.stream.events
> javax.xml.stream.util
> - JAF packages
> javax.activation
> [1]: http://cxf.apache.org/dosgi-releases.html
> [2]: http://jax-ws.java.net/2.2.7/docs/ch02.html#installation-instructions
> [3]: http://www.oracle.com/technetwork/java/javase/downloads/index-135046.html
> [4]: http://bugs.sun.com/view_bug.do?bug_id=6861589

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira