[mojo-dev] [jira] (MVERSIONS-272) Allow using display-plugin-updates without

[Jens Bannmann (JIRA)]

Title: Message Title

Jens Bannmann commented on an issue   Re: Allow using display-plugin-updates without <prerequisites> Looking at the mojo code, I found out that you do in fact iterate over the ancestor POMs, looking for the <prerequisites> element on each level. So there is in fact a workaround. However, one could say that you are (mis)using a Maven setting that applies to plugins and is not inherited to child projects as if it applied to all projects, and make it feel like it is inherited. So it would make still make sense to implement the suggestion above. Add Comment   Mojo's Versions Maven Plugin / MVERSIONS-272 Allow using display-plugin-updates without <prerequisites> The {{display-dependency-updates}} goal relies on the {{<prerequisites>}} element to find out the Maven version required by the current project. This is no longer a viable solution due to reasons given below. Starting with Maven 3.0, this element no longer has the desired effect: "enforcement of the build environment is left to the Maven Enforcer Plugi... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email