check version of nested plugins and dependencies specified inside some other
plugin
-----------------------------------------------------------------------------------
Key: MVERSIONS-137
URL: http://jira.codehaus.org/browse/MVERSIONS-137
Project: Maven 2.x Versions Plugin
Issue Type: Improvement
Reporter: Oleg Estekhin
The new maven-site-plugin:3.0 contains some plugins inside its
plugin/configuration/reportPlugins section. These plugins are not checked and
not reported by the versions:display-plugin-updates.
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.0-beta-3</version> <!-- this is checked -->
<configuration>
<reportPlugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.3</version> <!-- this is not checked -->
</plugin>
</reportPlugins>
</configuration>
</plugin>
{code}
Dependencies specified for a single plugin inside its plugin/dependencies
section are not checked and not reported by the
versions:display-dependency-updates.
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.5</version> <!-- this is checked -->
<dependencies>
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>5.1</version> <!-- this is not checked, the dependency is
just for demonstration -->
</dependency>
</dependencies>
</plugin>
{code}
These goals either should check such nested plugins/dependencies out of the
box, or check them when some additional parameter is specified, or there should
be separate goals that check nested plugins/dependencies only.
I assume that modifying versions:display-plugin-updates to understand nested
plugins will require specific handling for each plugin that can contain nested
plugins because each plugin can decide for its own path to nested plugins, but
at least site plugin with its plugin/configuration/reportPlugins should be
supported.
Modifying versions:display-dependency-updates to support dependencies nested
inside plugins should be more straight-forward as there only one possible path
for such dependencies (plugin/dependencies) which is standard for all plugins.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
