[WSS-241] WSS4j needs to export a version in it's Export-Package directive.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.8
• Fix Version/s: 1.5.9, 1.6
• Assignee: Colm O hEigeartaigh
• Reporter: Stanley J. Lewis
• Created: 20/Aug/10 14:13
• Updated: 15/Sep/10 22:55
• Resolved: 15/Sep/10 22:54

Description

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.