yep, it works with -DallowSnapshots=true, thanks. I got mistaken because of one example that was using -DallowSnapshots=false, I thought true was the default value.
I get it for the parent problem. I've been redirected to the version plugin by Maven folks about the automatic parent pom upgrade. We still have to wait for it to be fixed I guess. I've tried to deploy a new 3-SNAPSHOT version of my parent pom to the local repository. However, other machines wouldn't get the latest, just deployed version, with a <mvn versions:update-parent -DallowSnapshots=true>. It would only upgrade the pom with the latest found parent version, but not find out there's a newer SNAPSHOT in the repository, isn't it? cheers Stephen Connolly-2 wrote: > > 2008/12/22 nodje <[email protected]> > >> How would you configure the plugin so that it executes at each mvn >> execution? Or better, follow the regular Maven once-a-day update policy >> applied to the dependencies. >> > > That cannot ever work... > > Maven reads the pom when it starts... versions-maven-plugin changes the > pom... the pom on disk will not be the same as the pom that maven read in > before running versions-maven-plugin. > > You *always* have to run versions-maven-plugin on its own... > > e.g. > > mvn versions:update-parent -DallowSnapshots=true > mvn clean install > > Binding it to a phase will not do what you think it should do! > > -- View this message in context: http://www.nabble.com/Versions%3Aupdate-parent-usage-tp21125090p21139080.html Sent from the mojo - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
