Well, I'm not sure how to solve the problem in the xbean build.
Maven has not been designed to use more than one version of
the same dependency in the build, which leads to several problems.
One of them is that you can not downgrade a version, so you need to
use the oldest one and upgrade in other modules.
This means that xbean-spring depends on 1.2.4 or so.
When using xbean in servicemix, is usually end up adding a dependency
on spring in my pom with the correct version (2.0.1 for ex) and eventually
put it at the provided scope...
On 2/17/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On Sat, 17 Feb 2007 16:07 +0000 (GMT Standard Time), Terry Cox
<[EMAIL PROTECTED]> wrote:
> > Terry, what is the $xbean.version is used in the pom.xml?
>
> 2.8
>
> My code is built against the 3.1 release of ServiceMix.
>
> As an experiment, I just deleted all the 1.2.x versions of Spring from my
> repository and built ServiceMix 3.1 from source. Spring versions 1.2.4
> and 1.2.6 both re-appeared in the repository during the phase 1 build.
> Servicemix-core uses 1.2.4 and the xfire-maven-plugin uses 1.2.6.
>
> If you then check the build, you can see that the JSR-181 component build
> is over-riding the dependency management and substituting 1.2.6 instead
> of 2.0.1 so it looks as though there is some cross-contamination of
> Spring classes within ServiceMix.
Well evidently XBean 2.8 depends on Spring 1.2.4 which I don't
understand. I seem to recall that XBean used Spring 2.x so I'm rather
perplexed as to why a dep on Spring 1.2.4 is defined in the POM. I'm
sure Guillaume can shed some light on it, so let's wait for his
response.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
