Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.220.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALvzYd_YS-aVbCPL7CmEUGsUF0C3iskngEBdBd_9susy8KMcjQ@mail.gmail.com>
References: 
 <CALvzYd9zmmVkdEy3_A9s+EpTKV6QtEgDsYfCvtny6iLApwShcA@mail.gmail.com>
	<CAGB5yNnZai1KD=YSJbX8vzGKWZDAbZ6Yu4mLQapRaP+gGWb2jg@mail.gmail.com>
	<CALvzYd-sSwO5fq7dtQCiyex556NyQc2giP34vk9J_NfsLRf9RA@mail.gmail.com>
	<1368538636829-5732494.post@n5.nabble.com>
	<CALvzYd_YS-aVbCPL7CmEUGsUF0C3iskngEBdBd_9susy8KMcjQ@mail.gmail.com>
Date: Tue, 14 May 2013 21:39:43 +0200
Message-ID: 
 <CALvzYd8pK2=_d6yJb-wUCyaMP1x-m5z6QX0HcUiQC1HO+2+RJw@mail.gmail.com>
Subject: Re: Upgrade Spring 3.1.4.RELEASE -> 3.2.2.RELEASE
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: multipart/alternative; boundary=bcaec521618b852d1504dcb2cbed

--bcaec521618b852d1504dcb2cbed
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ok, I could fix it. All Camel features now works with Spring 3.2 and 3.1
I had to update the Karaf version to 2.3.2-SNAPSHOT to be able to use the
Spring 3.2 features provided by Karaf.

Best,
Christian


On Tue, May 14, 2013 at 8:48 PM, Christian M=FCller <
christian.mueller@gmail.com> wrote:

> Thanks Babak for pointing this out!
>
> The difference is:
> Spring 3.1:
> mvn:org.springframework/core/3.1.x <- OSGI bundle
>
> Spring 3.2:
> mvn:org.springframework/core/3.2.x <- normal JAR file
> mvn:org.springframework/org.springframework.core/3.2.x <- OSGI bundle
>
> Bad...
>
> The Spring 3.2 OSGI bundles are only available in the Spring EBR at [1]
>
> Bad again...
>
> This makes it really complicated to provide a feature file for Spring 3.1
> and 3.2. I will work on this now. The first goal is to get it working wit=
h
> Spring 3.2. Afterwards I will check what we can do to support Spring 3.1 =
as
> well.
>
> [1] http://repository.springsource.com/maven/bundles/release
>
> Best,
> Christian
>
>
> On Tue, May 14, 2013 at 3:37 PM, Babak Vahdat <babak.vahdat@swissonline.c=
h
> > wrote:
>
>> 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
>> Karaf
>> features validation on trunk is failing:
>>
>> ~/dev/workspace/camel/platforms>mvn clean install -Pvalidate
>> =85
>> ...
>> [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/class=
es/features.xml:
>> mvn:org.springframework/spring-context/3.2.2.RELEASE is not an OSGi bund=
le
>> -> [Help 1]
>> [ERROR]
>> [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]
>> [ERROR] For more information about the errors and possible solutions,
>> please
>> read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn <goals> -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 an=
y
>> 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.
>> >
>> > [1] http://svn.apache.org/viewvc?view=3Drevision&revision=3D1481748
>> >
>> > Best,
>> > Christian
>> >
>> >
>> > On Mon, May 13, 2013 at 6:44 PM, Claus Ibsen &lt;
>>
>> > claus.ibsen@
>>
>> > &gt; wrote:
>> >
>> >> 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=FCller
>> >> &lt;
>>
>> > christian.mueller@
>>
>> > &gt; wrote:
>> >> > I'm wondering whether we should use Spring 3.2.2.RELEASE by default
>> for
>> >> > 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
>> Karaf
>> >> > 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:
>>
>> > 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-Spring-3-1-4-RELEASE-3-2-2-REL=
EASE-tp5732377p5732494.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
>

--bcaec521618b852d1504dcb2cbed--