Re: [eclipselink-users] JPA: Toplink / Eclipselink works in Netbeans, no

[dyamanoha <ax.xaein@xxxxxxxxx>]

Ok, I figured it out.  I should have paid closer attention to my build
warnings -- maven was giving me a whole slue of warnings looking somewhat
similar to:

[WARNING] We have a duplicate javax/persistence/LockModeType.class in
C:\Users\David\.m2\repository\toplink\essentials\toplink-essentials\2.1-60f\toplink-essentials-2.1-60f.jar

Except instead of toplink, it was eclipselink.  I switched the order of my
maven dependencies to have eclipselink precede toplink and the problem was
fixed.  Apparently I was getting toplink service providers specified, in
Meta-INF/resources, and eclipselink wasn't able to overwrite them?  Anyway,
solution:


    <dependency>
      <groupId>org.eclipse.persistence</groupId>
      <artifactId>eclipselink</artifactId>
      <version>2.0.0</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>toplink.essentials</groupId>
      <artifactId>toplink-essentials</artifactId>
      <version>2.1-60f</version>
      <scope>compile</scope>
    </dependency>
-- 
View this message in context: http://old.nabble.com/JPA%3A-Toplink---Eclipselink-works-in-Netbeans%2C-not-as-standalone-.JAR-tp29528473p29816538.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.