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

Colm O hEigeartaigh reassigned WSS-241:
---------------------------------------

    Assignee: Colm O hEigeartaigh  (was: Ruchith Udayanga Fernando)

> WSS4j needs to export a version in it's Export-Package directive.
> -----------------------------------------------------------------
>
>                 Key: WSS-241
>                 URL: https://issues.apache.org/jira/browse/WSS-241
>             Project: WSS4J
>          Issue Type: Bug
>    Affects Versions: 1.5.8
>            Reporter: Stan Lewis
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.5.9, 1.6
>
>         Attachments: patch.txt
>
>
> If I install WSS4j into ServiceMix I see that the packages have no version 
> set, for example here's 1.5.8:
> WSS4J (120): org.apache.ws.security.message; version="0.0.0"
> WSS4J (120): org.apache.ws.security.saml; version="0.0.0"
> WSS4J (120): org.apache.ws.security.transform; version="0.0.0"
> WSS4J (120): org.apache.ws.axis.security.handler; version="0.0.0"
> WSS4J (120): org.apache.ws.security.components.crypto; version="0.0.0"
> WSS4J (120): org.apache.ws.security.action; version="0.0.0"
> WSS4J (120): org.apache.ws.security.message.token; version="0.0.0"
> WSS4J (120): org.apache.ws.security.conversation; version="0.0.0"
> WSS4J (120): org.apache.ws.security.handler; version="0.0.0"
> WSS4J (120): org.apache.ws.security.conversation.dkalgo; version="0.0.0"
> WSS4J (120): org.apache.ws.security.processor; version="0.0.0"
> WSS4J (120): org.apache.ws.security.util; version="0.0.0"
> WSS4J (120): org.apache.ws.security; version="0.0.0"
> WSS4J (120): org.apache.ws.axis.security; version="0.0.0"
> And here's 1.5.9-SNAPSHOT:
> WSS4J (182): org.apache.ws.security.saml; version="0.0.0"
> WSS4J (182): org.apache.ws.security.processor; version="0.0.0"
> WSS4J (182): org.apache.ws.axis.security.handler; version="0.0.0"
> WSS4J (182): org.apache.ws.axis.security; version="0.0.0"
> WSS4J (182): org.apache.ws.security.util; version="0.0.0"
> WSS4J (182): org.apache.ws.security.transform; version="0.0.0"
> WSS4J (182): org.apache.ws.security.conversation; version="0.0.0"
> WSS4J (182): org.apache.ws.security.handler; version="0.0.0"
> WSS4J (182): org.apache.ws.security.message.token; version="0.0.0"
> WSS4J (182): org.apache.ws.security.conversation.dkalgo; version="0.0.0"
> WSS4J (182): org.apache.ws.security.action; version="0.0.0"
> WSS4J (182): org.apache.ws.security.components.crypto; version="0.0.0"
> WSS4J (182): org.apache.ws.security; version="0.0.0"
> WSS4J (182): org.apache.ws.security.message; version="0.0.0"
> So it's not possible to have multiple versions running in the same OSGi 
> container.  Also noticed that the version of the felix-maven-bundle plugin 
> used is a bit old, so the patch I'm attaching fixes both issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscr...@ws.apache.org
For additional commands, e-mail: wss4j-dev-h...@ws.apache.org

Reply via email to