Thanks. We fixed the problem by locking down the version number of enforcer plugin. We're using maven 2.2.1.
But still I wonder about the behaviour when no version number has been specified... How are the version numbers determined by maven? How can it happen that maven uses a snapshot version as it is a maven convention that snapshot projects are at a development stage? Regards, Abid > On Thu, Nov 10, 2011 at 8:42 PM, Guo Du <mrdu...@duguo.org> wrote: > >> I wonder why maven uses a SNAPSHOT version of the plugin? > > Which maven version you use? > > > > A build log will helps to understand your problem. > > And best practice is to lock down the version numbers, which > ironically enforcer will tell you to do. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
