Incorrect OSGI versioning on milestone builds? [message #719312] |
Fri, 26 August 2011 12:56  |
Eclipse User |
|
|
|
I'm deploying an existing application that uses eclipselink 2.3.1-M2 to Virgo 3.0.0.RELEASE.
Virgo complains about the versioning scheme used, i.e. 2.3.1-M2 because it expects
major.minor.micro.qualifier as int,int,int,string (see osgi.org/javadoc/r4v43/org/osgi/framework/Version.html)
[2011-08-26 15:09:25.803] system-artifacts <DE0002E> Installation of plan 'my.plan' version '1.0.0' failed. java.lang.NumberFormatException: For input string: "1-M2"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at java.lang.Integer.parseInt(Integer.java:499)
at org.osgi.framework.Version.<init>(Version.java:135)
at org.osgi.framework.Version.parseVersion(Version.java:225)
at org.eclipse.virgo.util.osgi.VersionRange.<init>(VersionRange.java:78)
at org.eclipse.virgo.util.osgi.manifest.internal.BaseImported.getVersion(BaseImported.java:48)
I can see the line (119) in uploadToMaven.xml in the source where the - needs to change to a . but am completely unable to build it from the command line (missing an entire build.deps.dir for a start, and haven't used ant for years). I had hope to just build it and deploy to our local maven repo..
Thanks,
Jack
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04225 seconds