Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 67661 invoked from network); 25 Jun 2007 16:50:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2007 16:50:33 -0000 Received: (qmail 26399 invoked by uid 500); 25 Jun 2007 16:50:36 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 26371 invoked by uid 500); 25 Jun 2007 16:50:36 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 26362 invoked by uid 99); 25 Jun 2007 16:50:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 09:50:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of david.blevins@visi.com designates 208.42.156.9 as permitted sender) Received: from [208.42.156.9] (HELO cenn-smtp.mc.mpls.visi.com) (208.42.156.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 09:50:32 -0700 Received: from [10.0.1.2] (cpe-76-167-141-63.socal.res.rr.com [76.167.141.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by cenn-smtp.mc.mpls.visi.com (Postfix) with ESMTP id 07478812E for ; Mon, 25 Jun 2007 11:50:08 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v752.3) References: <467FE91F.1070809@apache.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7195EBC1-EEE0-4D19-A790-6AE55E8ED937@visi.com> Content-Transfer-Encoding: 7bit From: David Blevins Subject: Fwd: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble Date: Mon, 25 Jun 2007 09:49:57 -0700 To: dev@openjpa.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org 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: > From: Jeff Genender > Date: June 25, 2007 9:11:11 AM PDT > To: dev@openejb.apache.org, dev@geronimo.apache.org > Subject: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble > Reply-To: dev@geronimo.apache.org > Reply-To: jgenender@apache.org > > 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 >