Eclipse Community Forums: EclipseLink » Incorrect OSGI versioning on milestone builds?

Home » Eclipse Projects » EclipseLink » Incorrect OSGI versioning on milestone builds?

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

Re: Incorrect OSGI versioning on milestone builds? [message #719317 is a reply to message #719312]

Fri, 26 August 2011 13:27

Eclipse User

What bundle are you having trouble with? A quick check of the manifests of the org.eclipse.persistence.core and org.eclipse.persistence.jpa bundles in the 2.3.1 M3 bundle download shows a bundle-version of 2.3.1.v20110804-r9835.

--Shaun

Re: Incorrect OSGI versioning on milestone builds? [message #719323 is a reply to message #719317]

Fri, 26 August 2011 13:49

Eclipse User

Right now I don't know, I've been trying to locate/build a 2.3.1.M2 Smile

Upon reading your reply, I suspect the problem is that we define a property ${eclipse.persistence.version} to be 2.3.1-M2 and use it in our own pom files and template.mf files that we use with bundlor. This would mean that our own bundles have the problematic version info in their manifests. I'll take a look and relax the template.mf versioning to something like [2.3.1, 2.3.2]

Thanks,
Jack

Re: Incorrect OSGI versioning on milestone builds? [message #719333 is a reply to message #719323]

Fri, 26 August 2011 14:18

Eclipse User

Yes that was it, using a variable (that I introduced.. sigh) while upgrading caused the problem. Thanks for your help Shaun, it sent me to the solution.

Jack

Previous Topic:	[Solved] How can I set the defaultRowPrefetch size on the datasource?
Next Topic:	(no subject)

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 06:32:33 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter