maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCHANGES-150) [regression] Report Sets not honored during site goal
Date Thu, 26 Nov 2009 14:06:55 GMT

    [ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199588#action_199588
] 

Dennis Lundberg commented on MCHANGES-150:
------------------------------------------

I can confirm that this is a regression between versions 2.0 and 2.1 of Maven Changes Plugin.

However it has nothing to do with whether you are invoking the report via the "site" phase
or if you run the "changes:changes-report". You can use the following commands to verify it:

{noformat}
mvn org.apache.maven.plugins:maven-changes-plugin:2.0:changes-report

mvn org.apache.maven.plugins:maven-changes-plugin:2.1:changes-report
{noformat}

The first one will include the issue in the report, but the second one will not.

> [regression] Report Sets not honored during site goal
> -----------------------------------------------------
>
>                 Key: MCHANGES-150
>                 URL: http://jira.codehaus.org/browse/MCHANGES-150
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: changes-report
>    Affects Versions: 2.1
>            Reporter: Paul Benedict
>            Assignee: Brett Porter
>         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 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

        

Mime
View raw message