maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MCHANGES-150) [regression] Incorrect parsing of the <author> element
Date Wed, 30 Mar 2016 12:37:25 GMT

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

Michael Osipov commented on MCHANGES-150:
-----------------------------------------

Sadly, this issue still exists on every element which is either self-closing or has no content.
Must be a Modello thing.

> [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
>         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
(v6.3.4#6332)

Mime
View raw message