You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joshua Hyde (JIRA)" <ji...@codehaus.org> on 2011/09/01 15:59:34 UTC
[jira] Created: (MCHANGES-267) Add ability to skip JIRA report
creation
Add ability to skip JIRA report creation
----------------------------------------
Key: MCHANGES-267
URL: https://jira.codehaus.org/browse/MCHANGES-267
Project: Maven 2.x Changes Plugin
Issue Type: Improvement
Components: jira
Affects Versions: 2.6
Reporter: Joshua Hyde
Priority: Minor
Attachments: skip-jira.patch
We use the JIRA report in a reactor build, using Maven's reporting plugin inheritance to have child projects generate their own reports. However, some of the projects - such as the reactor build POMs themselves - have no real relevant JIRA components to be used in the report (they're just build aggregates). Right now, we just short-circuit the report in those cases by providing it a phony component ID, but it'd be nice if we could just skip it altogether, since our current approach still generates a JIRA report, but with an error message.
I've attached a patch with the proposed changes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHANGES-267) Add ability to skip JIRA report
creation
Posted by "Joshua Hyde (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Hyde updated MCHANGES-267:
---------------------------------
Attachment: skip-jira-username.patch
Just realized that the patch lists my computer's username, not my JIRA username, as the author on the test case. In case the @author tag survives the review process, I'm submitting a patch with the correct username so that traceability is a tad easier. :)
> Add ability to skip JIRA report creation
> ----------------------------------------
>
> Key: MCHANGES-267
> URL: https://jira.codehaus.org/browse/MCHANGES-267
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira
> Affects Versions: 2.6
> Reporter: Joshua Hyde
> Priority: Minor
> Attachments: skip-jira.patch, skip-jira-username.patch
>
>
> We use the JIRA report in a reactor build, using Maven's reporting plugin inheritance to have child projects generate their own reports. However, some of the projects - such as the reactor build POMs themselves - have no real relevant JIRA components to be used in the report (they're just build aggregates). Right now, we just short-circuit the report in those cases by providing it a phony component ID, but it'd be nice if we could just skip it altogether, since our current approach still generates a JIRA report, but with an error message.
> I've attached a patch with the proposed changes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-267) Add ability to skip JIRA report creation
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGES-267.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.8
Assignee: Dennis Lundberg
Patch applied in [r1382996|http://svn.apache.org/viewvc?view=revision&revision=1382996] with some modifications. The plugin has moved to using annotations for mojo parameters, so I adjusted the patch accordingly.
Thank you for the patch!
> Add ability to skip JIRA report creation
> ----------------------------------------
>
> Key: MCHANGES-267
> URL: https://jira.codehaus.org/browse/MCHANGES-267
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira
> Affects Versions: 2.6
> Reporter: Joshua Hyde
> Assignee: Dennis Lundberg
> Priority: Minor
> Fix For: 2.8
>
> Attachments: skip-jira.patch, skip-jira-username.patch
>
>
> We use the JIRA report in a reactor build, using Maven's reporting plugin inheritance to have child projects generate their own reports. However, some of the projects - such as the reactor build POMs themselves - have no real relevant JIRA components to be used in the report (they're just build aggregates). Right now, we just short-circuit the report in those cases by providing it a phony component ID, but it'd be nice if we could just skip it altogether, since our current approach still generates a JIRA report, but with an error message.
> I've attached a patch with the proposed changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira