[
http://jira.codehaus.org/browse/MCHANGES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252499#action_252499
]
Dennis Lundberg commented on MCHANGES-148:
------------------------------------------
This one would be tricky to implement. Personally I don't see the benefit of
having one aggregated report that spans over several projects that have
different release cycles.
> Add ability to pull from more than one Jira project and version
> ---------------------------------------------------------------
>
> Key: MCHANGES-148
> URL: http://jira.codehaus.org/browse/MCHANGES-148
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: jira
> Affects Versions: 2.1
> Reporter: Scott Coldwell
>
> We have projects that have multiple dependencies that correspond to separate
> Jira projects. We would like to be able to pull a report utilizing maven's
> dependency architecture to pull from multiple projects.
> For example:
> maven project: customer-project => Jira project: CUST-A
> maven project: my-lib => Jira project: MY-LIB
> maven project: my-other-lib => Jira project: MY-OTHERLIB
> customer-project 1.0 depends on my-lib version 2.0 and my-other-lib 3.0
> When generating a jira report we would want a way to automatically to maybe
> specify which dependencies would be included in the report.
> If the coniguration was something like:
> <configuration>
> <dependencies>
> <include>my-lib</include>
> </dependencies>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> </configuration>
> This would pull the report for CUST-A version 1.0 and MY-LIB 2.0 from Jira.
> If the coniguration was something like:
> <configuration>
> <dependencies>
> <include>my-*</include>
> </dependencies>
> <onlyCurrentVersion>true</onlyCurrentVersion>
> </configuration>
> This would pull the report for CUST-A version 1.0 and MY-LIB 2.0 AND
> MY-OTHERLIB 3.0 from Jira.
> Obviously there would have to be somewhere that maps the dependent projects
> to a Jira project. I'm not sure if the dependent project's pom could be
> leveraged for that. Possibly through the issueManagement url?
--
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
