[ http://jira.codehaus.org/browse/MPJIRA-11?page=all ]
Carlos Sanchez closed MPJIRA-11:
--------------------------------
Assign To: Carlos Sanchez (was: Emmanuel Venisse)
Resolution: Fixed
Fix Version: 1.2
Fixed as part of MPJIRA-13
> Enable retrieving component-specific issues
> -------------------------------------------
>
> Key: MPJIRA-11
> URL: http://jira.codehaus.org/browse/MPJIRA-11
> Project: maven-jira-plugin
> Type: Improvement
> Reporter: Arik Kfir
> Assignee: Carlos Sanchez
> Fix For: 1.2
> Attachments: jira-component.patch
>
>
> Many projects are divided into smaller components (managed in Maven via
> multiproject). Usually, the same structure is reflected in the project's JIRA
> - meaning a big project with each smaller project mapped to a JIRA
> *component*.
> If we add the JIRA report for such projects (that are part of a larger
> project), all subprojects will show all JIRA issues for the project, instead
> of the issues relevant to that specific component.
> Therefor, it would be useful to specify for the JIRA plugin to only query
> issues for a specific component, based on a plugin property. Then, each
> subproject will specify that property in its project.properties file, thus
> reflecting the true JIRA structure in the JIRA report.
> Attached to this issue is a patch I've made that makes it possible.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
