Eclipse Community Forums: EclipseLink » EclipseLink 2.7.4 and dependency jakarta.persistence signing problem

Home » Eclipse Projects » EclipseLink » EclipseLink 2.7.4 and dependency jakarta.persistence signing problem(signer information mismatch)

Show: Today's Messages :: Show Polls :: Message Navigator

EclipseLink 2.7.4 and dependency jakarta.persistence signing problem [message #1804516]

Thu, 28 March 2019 02:19

Dave Brosius

Messages: 34
Registered: July 2009

Member

I look at the pom for eclipselink 2.7.4 and see

<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>jakarta.persistence</artifactId>
<version>2.2.2</version>
</dependency>

That jar is signed, as see by contents of its manifest. It also has classes in common with what's found in eclipselink.jar, but the eclipse link jar is not signed. Thus when trying to use i get

java.lang.SecurityException: class "javax.persistence.Index"'s signer information does not match signer information of other classes in the same package

Is this a known issue?

Report message to a moderator

Re: EclipseLink 2.7.4 and dependency jakarta.persistence signing problem [message #1806038 is a reply to message #1804516]

Wed, 01 May 2019 08:21

Brett Sutton

Messages: 1
Registered: May 2019

Junior Member

Actually ignore my statement about the LocalDateTime problem.

I had managed to use a LocalDateTime from another package.

So in the end all I had to do was add a singular dependency which was:

group: org.eclipse.persistence
artifact: org.eclipse.persistence.jpa
version: 2.7.4'

and as noted before this is the version of the artifact that ends in '.jpa'

I do NOT appear to need
javax.persistence:javax.persistence-api:2.2

Report message to a moderator

Previous Topic:	unidirection @OneToOne+FetchType.LAZY not working
Next Topic:	ObjectBuilder extension

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jun 03 22:02:35 GMT 2023

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter