Matching plugin versions also removes custom configurations
-----------------------------------------------------------
Key: MNG-4045
URL: http://jira.codehaus.org/browse/MNG-4045
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.10, 2.0.9
Reporter: Paul Benedict
I was locking down my Maven Changes Plugin version with the following config:
{code}
<reporting>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.1</version>
<reportSets>
<reportSet>
<reports>
<report>changes-report</report>
</reports>
</reportSet>
</reportSets>
</plugin>
</reporting>
{code}
And then I created the site and noticed the report empty. The report markup was
there, of course, but it was like my changes.xml was blank. I could run
changes:changes-report just fine. However, when I then removed the <version>
tag and tried again, the report output was fine during site generation.
Here's an interesting line from the debug output when <version> is specified:
{quote}[DEBUG] The following artifacts were filtered out for plugin:
org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
the core of Maven:{quote}
My theory is that because my plugin version has an exact match on the version,
my specified plugin configuration is tossed. That certainly seems like a bug to
me.
--
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
