[
https://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MCHANGES-150.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> [regression] Incorrect parsing of the <author> element
> ------------------------------------------------------
>
> Key: MCHANGES-150
> URL: https://jira.codehaus.org/browse/MCHANGES-150
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: changes.xml, modello
> Affects Versions: 2.1
> Reporter: Paul Benedict
> Attachments: changes.xml, MNG-4045-debug.txt, MNG-4045.zip
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
