On 2009-8-14, at 上午9:05, boday wrote:
I feel like I'm running in circles trying to get the dependency
versions of
ServiceMix, Camel, Spring, Maven Plugins and namespaces to work well
together. Are others having issues with this?
I'm using SMX 3.3.1, Camel 1.6.1 and whatever spring-* versions that
come
over 2.0.5-2.5.6.
The servicemix-* components haven't been released for 3.3.1 yet, so,
I'm
using 3.2.3. Many examples/APIs require a newer version of Spring,
so I've
played around with different SMX versions that use the newer Spring
version...2009.01, etc.
Just one note here, after servicemix 3.3, we release servicemix
components and servicemix container separately(so that the components
could be shared by smx 3.x and 4.x), so the components version is
different with the container, for smx 3.3.1, it should use 2009.01,
hope this helps
Freeman
I've been working on setting up automated testing lately and have
run into a
whole new set of issues. Many of the examples don't work because
they need
a newer version of spring or camel, but if I add that dependency,
something
else breaks, etc...
Overall, I'm spending way too much time trying to manage
dependencies...
Is there a more stable version of these things that I should be
using? I'd
love to go to SMX 4 and Camel 2, but they haven't been formally
released
yet. Should I go to the FUSE releases?
I'm open to any advice at this point...thanks
-----
Ben - Senior Consultant
--
View this message in context:
http://www.nabble.com/ServiceMix-version-hell...-tp24963608p24963608.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
