Aha, just found the cause of this.. in my case, someone clobbered my Artifactory instance yesterday... sorry my fault for not thinking of checking on it before, thanks for your help anyway.
Regards, Ross Baptiste MATHUS-4 wrote: > > 2009/1/6 rossputin <rossaj...@yahoo.co.uk> > >> >> Can someone explain why the behaviour has changed.. was I remiss in not >> providing the version before, or did I miss out on an important >> announcement > > > In short, yes :-). Though it's a quite common mistake, it's good practice > to > always specify the versions of the plugin you're using. In fact, if you > don't, by default maven will look for the latest available version and it > might break your build if the default configuration changed. > >> >> explaining that I suddenly need to provide version information ? Perhaps >> I >> have done something to my pom which has upset the balance ? >> >> Additionally, now I have provided the version information, I am getting a >> complaint that the 'maven-default-skin' does not exist, I have not >> updated > > > I remember going into such kind of problem, but unfortunately I don't > remember what it was. > > Cheers. > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > > -- View this message in context: http://www.nabble.com/plugins-now-require-me-to-provide-a-version---tp21308561p21314979.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
