Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Complete
-
1.2.5.RELEASE
-
None
-
None
Description
On the following pom.xml:
...
<plugins>
<!-- plugin compiler -->
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven.compiler.plugin.version}</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<encoding>${project.build.sourceEncoding}</encoding>
<encoding>${project.build.sourceEncoding}</encoding>
</configuration>
</plugin>
<!-- plugin release -->
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<autoVersionSubmodules>true</autoVersionSubmodules>
<preparationGoals>clean verify</preparationGoals>
<goals>source:jar javadoc:jar install deploy</goals>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>${maven.aspect.plugin.version}</version>
<executions>
<execution>
<goals>
<goal>compile</goal>
</goals>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjtools</artifactId>
<version>${aspectj.version}</version>
</dependency>
</dependencies>
</plugin>
</plugins>
...
Some plugins appears without version.
This is not an error. Maven(3) accepts this omission and search the last version available of the plugin... but shows a WARNING indicating that this is not the best way to do it.
ROO should follow Maven practices, and only show a WARNING or Ignore it, not a throw EXCEPTION.