JPA version problem in odata4j-core OSGi manifest

[GoogleCodeExporter]

What steps will reproduce the problem?
I see that the OSGi manifest for odata4j-core has the following version 
requirements for JPA:
javax.persistence;version="[1.0.0,2.0.0)",
javax.persistence.metamodel;version="[2.0.0,3.0.0)",   

Note that javax.persistence version must be less than 2.0.

But the JPA version specified in the dependency of the pom.xml has:
<dependency>
    <groupId>org.eclipse.persistence</groupId>
    <artifactId>javax.persistence</artifactId>
    <version>${jpa.version}</version>
</dependency>   
and ${jpa.version} as specified in the parent pom.xml is
<jpa.version>2.0.0</jpa.version>

I don't believe it is possible to find a javax.persistence OSGi bundle that 
satisfies these version constraints.  I believe the manifest should be changed 
to:
javax.persistence;version="[2.0.0,3.0.0)",

What is the expected output? What do you see instead?
Unable to find an OSGi javax.persistence bundle that satsifies odata4j-core's 
manifest requirements.

What version of the product are you using? On what operating system?
0.7

Original issue reported on code.google.com by mark.los...@ca.com on 2 Nov 2012 at 5:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Seeing similar version problems in odata4j-core OSGi manifest for other bundles 
such as joda-time (version 2.1 is not supported by manifest but specified by 
the pom.xml) and eclipselink persistence (version 2.x is not supported by 
manifest but specified by the pom.xml).

This is making the odata4j-core pretty unusable within OSGi without manual 
modifications to the Manifest.mf

Original comment by mark.los...@ca.com on 2 Nov 2012 at 7:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks for feedaback. A fix is done. 

Original comment by stephan....@googlemail.com on 5 Nov 2012 at 9:46

• Changed state: Fixed