[ROO-3549] ROO Error when plugin doesn't have defined version on pom.xml Created: 07/Nov/14  Updated: 10/Nov/14  Due: 07/Nov/14  Resolved: 10/Nov/14

Status: Resolved
Project: Spring Roo
Component/s: None
Affects Version/s: 1.2.5.RELEASE
Fix Version/s: 1.3.0.RELEASE

Type: Bug Priority: Minor
Reporter: Juan Carlos García del Canto Assignee: Juan Carlos García del Canto
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 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.



 Comments   
Comment by Juan Carlos García del Canto [ 10/Nov/14 ]

Solved on https://github.com/spring-projects/spring-roo/commit/0a5efe6184954011275476703bbe10a24cc2b036 and https://github.com/spring-projects/spring-roo/commit/2808cb090d3c96922b60bcf778e87f3215d85880 commit

Generated at Fri Jan 24 05:37:31 UTC 2020 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.