It's a good practice to specify plugin version explicitly in your POM. Moreover, you can use a maven-enforcer-plugin that will validate whether you specified all versions explicitly. I would recommend to use it: http://maven.apache.org/plugins/maven-enforcer-plugin/
— Yegor Bugayenko, PMP®, SCEA On Thu, Mar 24, 2011 at 4:01 PM, David Balažic <[email protected]> wrote: > Ah, I see. Thanks. > > What is the next maven version that uses the 2.1 plugin by default? > > Regards, > David > > PS:Is maven.apache.org down currently? > http://www.downforeveryoneorjustme.com/maven.apache.org confirms that > it is not only me. > > On 24 March 2011 15:50, Benjamin Bentmann <[email protected]> > wrote: > > David Balažic wrote: > > > >> http://jira.codehaus.org/browse/MCOMPILER-70 > >> > >> I am using mvn --version > >> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > > > > Fix version for the above issue is maven-compiler-plugin 2.1, Maven 2.2.1 > > defaults to using maven-compiler-plugin 2.0.2. > > > > > > Benjamin > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
