[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167003#action_167003
]
Paul Benedict edited comment on MNG-4045 at 2/25/09 9:39 AM:
-------------------------------------------------------------
Attached is the Maven debug output, and an updated changes file.
Note how the report *contents* are only generated for the explicit
{{changes:changes-report}} goal, not the {{site:site}} goal.
Again, the only reason I think this is *not* a problem in the plugin is because
the <version> tag directly affects the test case. Put the tag in there, the
contents will generate for the site. Without the tag, it will be fine. I don't
see how that kind of high-level POM configuration could affect the plugin
itself, so my guess it's a "reactor" problem.
was (Author: paul4christ79):
Attached is the Maven debug output, and an updated changes file.
Note how the report *contents* are only generated for the explicit
{{changes:changes-report}} goal, not the {{site:site}} goal.
> Matching plugin versions also removes custom configurations
> -----------------------------------------------------------
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.0.10
> 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
