now that we are not targetting Maven 2.2.1 any more, we could avoid setting version on reports: version is taken from pluginManagement
the only little problem is that Maven 3.0 emits a warning that is a false positive: I think we can deal with it, isn't it? Regards, Hervé Le samedi 11 avril 2015 17:19:00 [email protected] a écrit : > Author: khmarbaise > Date: Sat Apr 11 17:19:00 2015 > New Revision: 1672903 > > URL: http://svn.apache.org/r1672903 > Log: > Consistent use of version 2.8 of maven-project-info-reports-plugin. > > Modified: > maven/pom/trunk/maven/pom.xml > > Modified: maven/pom/trunk/maven/pom.xml > URL: > http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=1672903&r1=1 > 672902&r2=1672903&view=diff > =========================================================================== > === --- maven/pom/trunk/maven/pom.xml (original) > +++ maven/pom/trunk/maven/pom.xml Sat Apr 11 17:19:00 2015 > @@ -1114,7 +1114,7 @@ under the License. > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-project-info-reports-plugin</artifactId> > - <version>2.7</version> > + <version>2.8</version> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
