maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Updated: (MNG-4045) Matching plugin versions also removes custom configurations
Date Wed, 25 Feb 2009 15:38:19 GMT


Paul Benedict updated MNG-4045:

    Attachment: changes.xml

Attached is the Maven debug output, and an updated changes file. 

Note how the report *contents* are only generated for the explicit {{changes:changes-report}}
goal, not the {{site:site}} goal.

> Matching plugin versions also removes custom configurations
> -----------------------------------------------------------
>                 Key: MNG-4045
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0.9, 2.0.10
>            Reporter: Paul Benedict
>            Assignee: Brett Porter
>         Attachments: changes.xml, MNG-4045-debug.txt,
> 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 was empty. The report markup was there,
of course, but it generated like my changes.xml was blank. I could run changes:changes-report
just fine. However, when I then removed the <version> tag and tried site:site again,
the report output was present as expected.
> 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:
For more information on JIRA, see:


View raw message