Re: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble
I think they need to push a SNAP...the current one is still stuck on JAXB 2.1. Jeff Jay D. McHugh wrote: > I think that they just added the dep within the past couple of weeks to > support having an xml datastore. > > I just saw on the OpenJPA list that they think that they could go back > to jaxb-2.0.2. > > Would that clear up questions on certification? > > Jay > > David Blevins wrote: >> I forwarded them your note and also went digging in scm archives as to >> why they added it. We'll see what they say. >> >> Have you tried adding an exclude on jaxb in the openjpa dep? And for >> the openejb dep we could exclude openjpa itself. >> >> -David >> >> On Jun 25, 2007, at 9:11 AM, Jeff Genender wrote: >> >>> 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 >>> >> >> >> >> . >>
[Fwd: Re: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble]
OpenJPA reverted back to jaxb 2.0 Jay --- Begin Message --- David, The jaxb dependency is changed to jaxb 2.0 by David Wisneski. Catalina On 6/25/07, David Blevins <[EMAIL PROTECTED]> wrote: On Jun 25, 2007, at 10:08 AM, catalina wei wrote: > David, > My XMLMaping test cases run with jaxb 2.0.2. > Would jaxb dependency change to jaxb 2.0.2 work for you ? I think that will work, thanks. Geronimo is using 2.0.5. Not sure which version EasyBeans/JOnAS may be using. -David > Catalina > > On 6/25/07, David Blevins <[EMAIL PROTECTED]> wrote: >> >> 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 >> > >> >> --- End Message ---
Re: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble
I think that they just added the dep within the past couple of weeks to support having an xml datastore. I just saw on the OpenJPA list that they think that they could go back to jaxb-2.0.2. Would that clear up questions on certification? Jay David Blevins wrote: I forwarded them your note and also went digging in scm archives as to why they added it. We'll see what they say. Have you tried adding an exclude on jaxb in the openjpa dep? And for the openejb dep we could exclude openjpa itself. -David On Jun 25, 2007, at 9:11 AM, Jeff Genender wrote: 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 .
Re: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble
I forwarded them your note and also went digging in scm archives as to why they added it. We'll see what they say. Have you tried adding an exclude on jaxb in the openjpa dep? And for the openejb dep we could exclude openjpa itself. -David On Jun 25, 2007, at 9:11 AM, Jeff Genender wrote: 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
