"alesj" wrote : "adrian(a)jboss.org" wrote : | | However Maven doesn't use that scheme: | | http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+... | | instead it is | | major.minor.micro-qualifier-build | | | | So our | | jboss-5.0.0.Beta4 | | should be under maven | | jboss-5.0.0-Beta-4 | | for the version ranges to work properly. | Can't you hack this? | e.g. first trying how maven wants it, then also try our own | So that the old stuff would still work. I was planning to bring up better support for the OSGi format on the maven dev list. Currently when maven tries to parse the last "." (instead of a "-") of our versions, it decides that we're using a non standard format and gives up on trying to parse it. If it seems worthwhile I can try to change the version number parsing so that it parses everything after the fourth dot as a qualifier or something like that to better handle OSGi. I don't understand enough about how OSGi works, but as a second option, can we translate the maven version to something OSGi compatible in our builds? So maybe use the maven standard versions in our poms, but then put the equivalent OSGi version string into jar metadata, or somewhere else that it can be used? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140214#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...