maven-wagon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Shue" <>
Subject wagon-induced infinite build loop
Date Tue, 19 Oct 2010 17:46:19 GMT
I'm struggling with the infinite rebuild loop in Eclipse, which might be
caused by an old Wagon bug.  The bug is described here and, and someone
indicated that this Wagon bug might be the culprit:


My question is, how can I get the latest version of Wagon on my build?
If I delete the Wagon directory in my local Maven repo, and run "mvn
compile", I always get 1.0-alpha-6 and 1.0-beta-2 brought down.  These
are old versions of Wagon.


I have taken our company parent POM and updated all the plugins listed
there to the latest version I could find in the central maven repo.  I
have added Wagon 1.0-beta-6 to the dependencyManagement section of my
POM.  I've used Maven 3, both with and without my company parent POM.  I
still get those old versions.


How can I force maven to use a later version of Wagon?  How could I find
out who/what is bringing Wagon into my build?


Thanks for any help you can give!


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message