You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@santuario.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2013/06/07 17:22:22 UTC

[jira] [Created] (SANTUARIO-356) Expand OSGi import versions for javax.xml.crypto*

Daniel Kulp created SANTUARIO-356:
-------------------------------------

             Summary: Expand OSGi import versions for javax.xml.crypto*
                 Key: SANTUARIO-356
                 URL: https://issues.apache.org/jira/browse/SANTUARIO-356
             Project: Santuario
          Issue Type: Bug
          Components: Java
    Affects Versions: Java 2.0.0
            Reporter: Daniel Kulp
            Assignee: Colm O hEigeartaigh



Currently on trunk, the xmlsec osgi bundle exports the javax.xml.crypto packages with 2.0.0-SNAPSHOT version number.  However, that means applications that use the bundle plugin and are compiled against xmlsec, but ONLY use the javax.xml.crypto classes will not work with 2.0.0-SNAPSHOT even though those standard API's haven't changed.    

Two approaches:
1) Export those packages with both 2.0.0-SNAPSHOT and the 1.5.4 version number.  (patch attached for this)

2) Split the javax.xml.crypto stuff into it's own bundle/jar which can have it's own version numbers.



--
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