[jira] [Commented] (MCHANGES-150) [regression] Incorrect parsing of the element

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000216#comment-17000216 ] 

Elliotte Rusty Harold commented on MCHANGES-150:
------------------------------------------------

sounds like this might be more important than just this one case

> [regression] Incorrect parsing of the <author> element
> ------------------------------------------------------
>
>                 Key: MCHANGES-150
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-150
>             Project: Maven Changes Plugin
>          Issue Type: Bug
>          Components: changes.xml, modello
>    Affects Versions: 2.1
>            Reporter: Paul Benedict
>            Priority: Major
>         Attachments: MNG-4045-debug.txt, MNG-4045.zip, changes.xml
>
>
> 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
(v8.3.4#803005)