You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wagon-users@maven.apache.org by David Shue <da...@babycenter.com> on 2010/10/19 19:46:19 UTC
wagon-induced infinite build loop
I'm struggling with the infinite rebuild loop in Eclipse, which might be
caused by an old Wagon bug. The bug is described here
https://issues.sonatype.org/browse/MNGECLIPSE-1885 and
https://issues.sonatype.org/browse/MNGECLIPSE-2239, and someone
indicated that this Wagon bug might be the culprit:
http://jira.codehaus.org/browse/WAGON-73.
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!