You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/08/18 21:47:32 UTC
[jira] Commented: (MCHANGES-150) [regression] Report Sets not
honored during site goal
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232372#action_232372 ]
Dennis Lundberg commented on MCHANGES-150:
------------------------------------------
After some digging I've found the source of the problem. Your sparse, but correct, usage of the author element is parsed incorrectly by the Modello generated parser.
{noformat}
<author email="pbenedict@apache.org"/>
{noformat}
results in this xhtml code:
{noformat}
<meta name="author" content="<author email="pbenedict@apache.org"/>" />
{noformat}
I've tried upgrading to a newer version of Modello, but that results in test failures.
> [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
> 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