[mojo-dev] [jira] (MVERSIONS-207) No longer print "missing version #" warnings for plugins defined via parent

[Glen Mazza (JIRA)]

Glen Mazza commented on MVERSIONS-207 No longer print "missing version #" warnings for plugins defined via parent <pluginManagement/> The two IT tests that failed are as follows: [ERROR] * it-display-plugin-updates-005/pom.xml [ERROR] * it-display-plugin-updates-006/pom.xml A test is defined by three files: the pom.xml, verify.bsh, and invoker.properties. The pom.xml and verify.bsh are equivalent in both test cases. The only difference between the two is that 005's invoker.properties has this: invoker.goals=${project.groupId}:${project.artifactId}:${project.version}:display-plugin-updates (correct – running 3.0-SNAPSHOT of versions plugin as a result) ...while it-display-plugin-updates-006/pom.xml just runs the current production version of the plugin on my machine (currently 1.3.1): invoker.goals=versions:display-plugin-updates I'm unsure what the point is in doing an IT test on a current production version of the plugin instead of the SNAPSHOT version. None of the other IT tests, and I've checked them all, just call mvn versions:blah in their invoker.properties, it's always ${project.groupId}:${project.artifactId}:... to get the version being tested. Further, there's no comment given in the invoker.properties for why this test in being run. I think the it-display-plugin-updates-006 test can be removed from the source repo, as it's not testing the SNAPSHOT version. Analysis on it-display-plugin-updates-005 next...

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email