Hi Sahoo,

As a workaround for this started using a special version numbering scheme to come around this problem: Bundles are released with an even micro number (e.g. 1.0.0 or 1.0.2 or 1.2.6) and SNAPSHOT versions have an odd micro number (e.g. 1.0.1-SNAPSHOT, 1.2.5-SNAPSHOT).

This guarantees that the snapshot of the next release always comes before the next release and that the snapshot after a release always comes after a release.

Look for example at the Apache Felix scr, configadmin and metatype bundles (there is an exception for configadmin, which has a 1.0.1 release. This will be fixed for the next release).

Hope this helps.

Regards
Felix

Sahoo schrieb:
I do understand the two systems were developed independently, and I am not expecting any of the two systems to change, but what I am hoping to find out is that if there is a scope for maven-bundle-plugin to address this issue.

Thanks,
Sahoo

Richard S. Hall wrote:
I would guess this is just a general OSGi vs Maven version numbering scheme mismatch. The qualifier portion of a version in OSGi is just sorted lexical order, if I recall, so it is not possible to make no qualifier come after one with a qualifier, since an empty string always comes before a non-empty string.

So, in short, it isn't right, but there isn't much we can do about it, I guess. The two systems were developed independently.

-> richard

Sahoo wrote:
AFAIK, Maven considers x-SNAPSHOT to be earlier than x, where as the corresponding OSGi versions as generated by [1], which is used by maven-bundle-plugin, behave just the opposite. This does not seem right to me.

Thanks,
Sahoo

[1] http://svn.apache.org/repos/asf/maven/shared/tags/maven-osgi-0.2.0/src/main/java/org/apache/maven/shared/osgi/DefaultMaven2OsgiConverter.java

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to