Hey guys, figured this thread belonged here. See below.
I looked through the archives to see what the change related to and
it looks like OPENJPA-240 was it. If we found a way in Geronimo to
force OpenJPA back onto jaxb 2.0 so we could continue to certify
javaee6 would things still work sans this feature?
Also, any idea how much longer it may be for a 1.0.0 release?
I know it's tough to balance user and integrator needs, so thanks in
advance for any help.
-David
Begin forwarded message:
Resent-From: <[EMAIL PROTECTED]>
From: Jeff Genender <[EMAIL PROTECTED]>
Date: June 25, 2007 9:11:11 AM PDT
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble
Reply-To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Hi,
I am sending this to the G and OEJB lists.
We have dependencies on OpenJPA SNAPSHOT in trunk. Looks like they
moved to jaxb 2.1 and this is causing troubles with building.
First its having trouble finding javax.xml.stream:stax-api:jar:1.0-2,
and second, I am fairly confident this is going to impact
certification.
Thoughts?
Jeff