Build gets extra dependencies.

[dchicks]

I've got an automated build that runs on Hudson that is producing a WAR
that cannot load and run.  It appears that it is picking up extra
dependencies during the build process.  One of those is
spring-2.0.6.jar.  I believe this is causing my load/run problem because
the error I get is related to loading the Spring context.  My question
is simply this...

Can anyone tell me why a Maven build would pick up extra dependencies if
everything appears to be the same between two machines.  Same JDK, same
version of Maven, same settings.xml in .m2, same build command ("mvn
clean install").  Yet, the automated build ends up with 5 extra jars in
the WEB-INF/lib directory.  I'm stumped, and this is causing us a world
of problems.

Thanks in advance.
Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Jörg Schaible-2]

David C. Hicks wrote at Mittwoch, 1. Juli 2009 00:18:

> I've got an automated build that runs on Hudson that is producing a WAR
> that cannot load and run.  It appears that it is picking up extra
> dependencies during the build process.  One of those is
> spring-2.0.6.jar.  I believe this is causing my load/run problem because
> the error I get is related to loading the Spring context.  My question
> is simply this...
>
> Can anyone tell me why a Maven build would pick up extra dependencies if
> everything appears to be the same between two machines.  Same JDK, same
> version of Maven, same settings.xml in .m2, same build command ("mvn
> clean install").  Yet, the automated build ends up with 5 extra jars in
> the WEB-INF/lib directory.  I'm stumped, and this is causing us a world
> of problems.

The artifacts of your repository might have been loaded from different
repos. Repo at java.net and JBoss tend to have sometimes different POMs for
artifacts that are also available on Maven central or (at least java.net)
redeploys already released artifacts ;-/

Therefore ensure that you setup a mirror for anything in settings.xml and
use a proxy/archive manager with a well-defined sequence for the repos to
search for artifacts.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[dchicks]

It turns out that the spring-2.0.6.jar was a transitive dependency.  The
really strange part is that by simply deleting my local repository and
letting it rebuild as the build proceeded, that dependency magically
vanished.  That, I don't get.  Unfortunately, I don't have much time to
"play" with it, right now.  I'll just have to accept that we're in good
shape (for now) and move on.  Weird!

Jörg Schaible wrote:

> David C. Hicks wrote at Mittwoch, 1. Juli 2009 00:18:
>
>  
>> I've got an automated build that runs on Hudson that is producing a WAR
>> that cannot load and run.  It appears that it is picking up extra
>> dependencies during the build process.  One of those is
>> spring-2.0.6.jar.  I believe this is causing my load/run problem because
>> the error I get is related to loading the Spring context.  My question
>> is simply this...
>>
>> Can anyone tell me why a Maven build would pick up extra dependencies if
>> everything appears to be the same between two machines.  Same JDK, same
>> version of Maven, same settings.xml in .m2, same build command ("mvn
>> clean install").  Yet, the automated build ends up with 5 extra jars in
>> the WEB-INF/lib directory.  I'm stumped, and this is causing us a world
>> of problems.
>>    
>
> The artifacts of your repository might have been loaded from different
> repos. Repo at java.net and JBoss tend to have sometimes different POMs for
> artifacts that are also available on Maven central or (at least java.net)
> redeploys already released artifacts ;-/
>
> Therefore ensure that you setup a mirror for anything in settings.xml and
> use a proxy/archive manager with a well-defined sequence for the repos to
> search for artifacts.
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...