Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » java.lang.SecurityException: signer information does not match signer information of other classes i
java.lang.SecurityException: signer information does not match signer information of other classes i [message #658172] Mon, 07 March 2011 04:15
Eclipse User
Originally posted by: james.ractive.ch

Hello everyone

I'm trying to get the maven-processor-plugin to execute the
EclipseLink's CanonicalModelProcessor to generate metamodels for JPA.
I'm following the blog entry
http://blog.gueck.com/2009/12/generating-jpa-20-criteria-can onical.html
that describes how to set up this with Maven.

When executing mvn generate-sources, I get the following exception:

[INFO] diagnostic error: java.lang.SecurityException: class
" org.eclipse.persistence.internal.jpa.modelgen.CanonicalModel Properties "'s
signer information does n
ot match signer information of other classes in the same package


An annotation processor threw an uncaught exception.
Consult the following stack trace for details.
java.lang.RuntimeException: java.lang.SecurityException: class
" org.eclipse.persistence.internal.jpa.modelgen.CanonicalModel Properties "'s
signer information doe
s not match signer information of other classes in the same package
at
org.eclipse.persistence.internal.jpa.modelgen.CanonicalModel Processor.process(CanonicalModelProcessor.java:407)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.ca llProcessor(JavacProcessingEnvironment.java:625)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.di scoverAndRunProcs(JavacProcessingEnvironment.java:554)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.do Processing(JavacProcessingEnvironment.java:699)
at
com.sun.tools.javac.main.JavaCompiler.processAnnotations(Jav aCompiler.java:981)
at
com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.j ava:727)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
....


I think that this is caused by two concurring versions of eclipselink.
My project depends on the OSGI version, but the maven-processor-plugin
on the "normal" eclipselink version. The OSGI version is signed, the
normal version not. The plugin has to use the normal version, because
the CanonicalModelProcessor only is contained in this jar.



<dependencies>
....
<dependency>
<!-- signed OSGI version -->
<groupId>org.eclipse.persistence</groupId>
<artifactId>org.eclipse.persistence.jpa</artifactId>
<scope>compile</scope>
</dependency>
....
</dependencies>


<plugin>
<groupId>org.bsc.maven</groupId>
<artifactId>maven-processor-plugin</artifactId>
<dependencies>

<dependency>
<!-- unsigned OSGI version -->
<groupId>org.eclipse.persistence</groupId>
<artifactId>eclipselink</artifactId>
<version>${eclipselink.version}</version>
</dependency>
</dependencies>
.....
</plugin>




Do you have any ideas how I can get around this security exception?


Thanks in advance,
James
Previous Topic:Dynamic Moxy accessing enum values
Next Topic:Help on caching needed
Goto Forum:
  


Current Time: Sat Jul 26 15:14:35 EDT 2014

Powered by FUDForum. Page generated in 0.02202 seconds