Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 77944 invoked from network); 25 Jun 2007 17:09:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2007 17:09:09 -0000 Received: (qmail 86822 invoked by uid 500); 25 Jun 2007 17:09:12 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 86787 invoked by uid 500); 25 Jun 2007 17:09:12 -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 86778 invoked by uid 99); 25 Jun 2007 17:09:11 -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 10:09:11 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of catalina.wei@gmail.com designates 66.249.82.230 as permitted sender) Received: from [66.249.82.230] (HELO wx-out-0506.google.com) (66.249.82.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 10:09:07 -0700 Received: by wx-out-0506.google.com with SMTP id h26so1562577wxd for ; Mon, 25 Jun 2007 10:08:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=GP3ekHF5SabbpEzrEuIZSKNl7IM0APp1m5CxJ6/WNSVaAykK/OJTIbezgK9AXrPCqLa0Kd5bjJmb9RfTiaDKBPus7ZY1TjKTgxExUjeBjL4stgv/yOiqNZ32s0gof6KiX78cOpGXY7cVVSEJDIsVzvb3TnQ7Whh/wx2GsYk/K5g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=F6i1cNYF3er+TVeNxP34aeP01/WBS2FvuQGQyIzxekScb2mecqfHmtMN9XmfTO6KAq0W/n+hkkVfQY7BQtLaggXetaJTUzNd2/xHMX3U9ntX401i2QGMNWoOBobnX4DOZOBa9TJgKYSDTwXZ2RsGYbjPgLi+7lEkmCVake5Zffg= Received: by 10.70.98.17 with SMTP id v17mr9630940wxb.1182791326848; Mon, 25 Jun 2007 10:08:46 -0700 (PDT) Received: by 10.70.42.12 with HTTP; Mon, 25 Jun 2007 10:08:46 -0700 (PDT) Message-ID: Date: Mon, 25 Jun 2007 10:08:46 -0700 From: "catalina wei" To: dev@openjpa.apache.org Subject: Re: OpenJPA moved to JAXB 2.1 and this is gonna cause trouble In-Reply-To: <7195EBC1-EEE0-4D19-A790-6AE55E8ED937@visi.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_127889_12112663.1182791326817" References: <467FE91F.1070809@apache.org> <7195EBC1-EEE0-4D19-A790-6AE55E8ED937@visi.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_127889_12112663.1182791326817 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline David, My XMLMaping test cases run with jaxb 2.0.2. Would jaxb dependency change to jaxb 2.0.2 work for you ? Catalina On 6/25/07, David Blevins 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: > > 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 > > > > ------=_Part_127889_12112663.1182791326817--