Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D07929FFD for ; Tue, 14 May 2013 13:38:08 +0000 (UTC) Received: (qmail 19582 invoked by uid 500); 14 May 2013 13:38:08 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 19319 invoked by uid 500); 14 May 2013 13:38:05 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 19295 invoked by uid 99); 14 May 2013 13:38:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 13:38:04 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=URI_HEX X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 May 2013 13:37:59 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UcFPo-0002Ps-R4 for dev@camel.apache.org; Tue, 14 May 2013 06:37:16 -0700 Date: Tue, 14 May 2013 06:37:16 -0700 (PDT) From: Babak Vahdat To: dev@camel.apache.org Message-ID: <1368538636829-5732494.post@n5.nabble.com> In-Reply-To: References:

Subject: Re: Upgrade Spring 3.1.4.RELEASE -> 3.2.2.RELEASE MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Just wonder if the current Karaf 2.3.x SVN code base really supports Spring 3.2.x as it's no longer OSGi complaint. This is also why currently our Kara= f features validation on trunk is failing: ~/dev/workspace/camel/platforms>mvn clean install -Pvalidate =E2=80=A6 ... [ERROR] Failed to execute goal org.apache.karaf.tooling:features-maven-plugin:2.3.1:validate (validate) on project apache-camel: Unable to validate /Users/bvahdat/dev/workspace/camel/platforms/karaf/features/target/classes/= features.xml: mvn:org.springframework/spring-context/3.2.2.RELEASE is not an OSGi bundle -> [Help 1] [ERROR]=20 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR]=20 [ERROR] For more information about the errors and possible solutions, pleas= e read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR]=20 [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :apache-camel I assume if we would properly switch our Maven build to SpringSource EBR then the problem should be fixed, for more details see: http://www.springsource.org/springframework-ebr I also checked the the Karaf 2.3.x branch code base and couldn't find any usage of SpringSource EBR but maybe I missed something. Babak Christian Mueller wrote > JB added the Spring 3.2 support to Karaf 2.3.x today [1]. > I will go ahead and make Spring 3.2 as the default and set up a Spring 3.= 1 > CI build as well. >=20 > [1] http://svn.apache.org/viewvc?view=3Drevision&revision=3D1481748 >=20 > Best, > Christian >=20 >=20 > On Mon, May 13, 2013 at 6:44 PM, Claus Ibsen < > claus.ibsen@ > > wrote: >=20 >> Hi >> >> Yeah I think it would be good to upgrade to Spring 3.2.x for Camel 2.12. >> Certainly if Karaf / SMX will support that version as well. >> >> On Sun, May 12, 2013 at 11:45 PM, Christian M=C3=BCller >> < > christian.mueller@ > > wrote: >> > I'm wondering whether we should use Spring 3.2.2.RELEASE by default fo= r >> > Camel 2.12.x. >> > This version is stable and by still supporting Spring 3.1.x (with a >> > separate CI build), we can make sure Camel 2.12.x is working with Kara= f >> > 2.3.1. >> > Starting with Karaf 2.3.2, Karaf comes with a Spring 3.2 feature [1]. >> Karaf >> > 2.3.2 is expected for the next two/three weeks [2]. >> > >> > What do you think? >> > >> > [1] https://issues.apache.org/jira/browse/KARAF-2062 >> > [2] >> > >> http://karaf.922171.n3.nabble.com/DISCUSSION-Apache-Karaf-2-3-2-and-3-0-= 0-RC2-in-two-weeks-time-td4028632.html >> > >> > Best, >> > Christian >> >> >> >> -- >> Claus Ibsen >> ----------------- >> www.camelone.org: The open source integration conference. >> >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Email:=20 > cibsen@ >> Web: http://fusesource.com >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen >> -- View this message in context: http://camel.465427.n5.nabble.com/Upgrade-Spr= ing-3-1-4-RELEASE-3-2-2-RELEASE-tp5732377p5732494.html Sent from the Camel Development mailing list archive at Nabble.com.