Community
Participate
Working Groups
Build Identifier: 1.1.0.M01 This issue is more of a Maven snapshot version syntax versus OSGi version syntax issue. Maven Virgo Bundlor defaults the "Bundle-Version" header to the Maven value ${project.version}. If you're using snapshots (very often, IMHO), then you're version is suffixed with "-SNAPSHOT", resulting in, for example, a project version of 1.0.0-SNAPSHOT. This is not a valid OSGi version string due to the dash instead of a dot after the micro element. With this issue I'm requesting a reasonable default algorithm to be put in place rather than having the developer manage the version himself. Given most Maven projects use a version syntax of major ["." minor ["." micro ["qualifier"]]] which is not far from OSGi's major "." minor "." micro ["." "qualifier"] it seems that a reasonable default algorithm can be supplied to OSGi-ify the Maven version string. Reproducible: Always Steps to Reproduce: 1. Use a Maven snapshot project with the "-SNAPSHOT" suffix. 2. Use the Virgo Bundlor without specifying a Bundle-Version. 3. Observe that the resultant Bundle-Version is not OSGi compliant.
A reasonable solution to this is to use version like 1.0.0.BUILD-SNAPSHOT in maven projects. Works well with OSGi and Maven.
Nice. I should've remembered that -- it's used frequently.
Does comment 1 address this bug so that we can close it or set WONT_FIX or would you still like to see another solution?
(In reply to comment #3) > Does comment 1 address this bug so that we can close it or set WONT_FIX or > would you still like to see another solution? WONT_FIX is fine.
Thanks Matthew!
