You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2009/02/19 17:59:19 UTC
[jira] Created: (MNG-4045) Matching plugin versions also removes
custom configurations
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.10, 2.0.9
Reporter: Paul Benedict
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 empty. The report markup was there, of course, but it was like my changes.xml was blank. I could run changes:changes-report just fine. However, when I then removed the <version> tag and tried again, the report output was fine during site generation.
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
[jira] Commented: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166901#action_166901 ]
Paul Benedict commented on MNG-4045:
------------------------------------
Brett, I think you misunderstood the issue. The changes.xml file is always present. It's only when I put in the <version> of the plugin that it does not generate in the 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: 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
[jira] Updated: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-4045:
-------------------------------
Attachment: changes.xml
MNG-4045-debug.txt
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
[jira] Commented: (MCHANGES-150) Matching plugin versions tosses
specified report sets
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167095#action_167095 ]
Brett Porter commented on MCHANGES-150:
---------------------------------------
I'm guessing that when you remove the version, you get v2.0 due to some old metadata in your environment. I misunderstood what you meant by "empty" - the report has no rows, but is still generated. This comes up correctly in 2.0, but not in 2.1
Therefore, it is a regression in the changes plugin for the format of your changes file.
> Matching plugin versions tosses specified report sets
> -----------------------------------------------------
>
> 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
[jira] Updated: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-4045:
-------------------------------
Description:
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.
was:
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 empty. The report markup was there, of course, but it was like my changes.xml was blank. I could run changes:changes-report just fine. However, when I then removed the <version> tag and tried again, the report output was fine during site generation.
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.
> 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
>
> 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
[jira] Commented: (MCHANGES-150) [regression] Report Sets not
honored during site goal
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166860#action_166860 ]
Paul Benedict commented on MNG-4045:
------------------------------------
Isn't the <reportSets> part of the configuration? If I mislabeled this issue, I apologize. So the reportSets get tossed?
> 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
>
> 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
[jira] Commented: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166858#action_166858 ]
Brett Porter commented on MNG-4045:
-----------------------------------
where is the report configuration in this POM?
> 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
>
> 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
[jira] Reopened: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict reopened MNG-4045:
--------------------------------
I am reopening this because I can reproduce it. If we can re-determine it is actually a problem with the Changes Plugin, I will move this issue into that project. I will be attaching updated documents in the next comment.
> 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: 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
[jira] Closed: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-4045.
-----------------------------
Assignee: Brett Porter
Resolution: Cannot Reproduce
this wasn't a direct cut and paste (there is a missing <plugins> element), so there's a chance it was mistyped in your original POM.
If it is correct, I would put this down to a different version of the changes plugin behaving differently based on the existence of src/changes/changes.xml. The report is not generated if that file is missing in 2.1. Maybe it is in a different version that you get with the version removed. Either way, this isn't a Maven issue AFAICT.
> 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: 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
[jira] Issue Comment Edited: (MNG-4045) Matching plugin versions
also removes custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MCHANGES-150) [regression] Report Sets not honored
during site goal
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-150:
-------------------------------------
Component/s: modello
> [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.xml, modello
> 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
[jira] Updated: (MNG-4045) Matching plugin versions tosses
specified report sets
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-4045:
-------------------------------
Summary: Matching plugin versions tosses specified report sets (was: Matching plugin versions also removes custom configurations)
> Matching plugin versions tosses specified report sets
> -----------------------------------------------------
>
> 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
[jira] Commented: (MCHANGES-150) [regression] Report Sets not
honored during site goal
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Moved: (MCHANGES-150) Matching plugin versions tosses
specified report sets
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-4045 to MCHANGES-150:
--------------------------------------------
Affects Version/s: (was: 2.0.10)
(was: 2.0.9)
2.1
Component/s: (was: Plugins and Lifecycle)
changes-report
Key: MCHANGES-150 (was: MNG-4045)
Project: Maven 2.x Changes Plugin (was: Maven 2)
> Matching plugin versions tosses specified report sets
> -----------------------------------------------------
>
> 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
[jira] Updated: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4045:
------------------------------
Attachment: MNG-4045.zip
see attached test project where it works just fine
> 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
> Attachments: 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
[jira] Commented: (MNG-4045) Matching plugin versions also removes
custom configurations
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166932#action_166932 ]
Brett Porter commented on MNG-4045:
-----------------------------------
that's what I understood, and is consistent with my comment. does the attached sample project work for you?
> 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: 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
[jira] Updated: (MCHANGES-150) [regression] Report Sets not honored
during site goal
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MCHANGES-150:
-----------------------------------
Summary: [regression] Report Sets not honored during site goal (was: Matching plugin versions tosses specified report sets)
> [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
[jira] Updated: (MCHANGES-150) [regression] Report Sets not honored
during site goal
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MCHANGES-150:
----------------------------------
Assignee: (was: Brett Porter)
> [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
[jira] Updated: (MCHANGES-150) [regression] Incorrect parsing of
the element
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MCHANGES-150:
-------------------------------------
Summary: [regression] Incorrect parsing of the <author> element (was: [regression] Report Sets not honored during site goal)
> [regression] Incorrect parsing of the <author> element
> ------------------------------------------------------
>
> Key: MCHANGES-150
> URL: http://jira.codehaus.org/browse/MCHANGES-150
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes.xml, modello
> 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
[jira] Issue Comment Edited: (MNG-4045) Matching plugin versions
also removes custom configurations
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ 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 not 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.
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.
> 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