Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Auto Closed
-
2.1
-
None
-
None
Description
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?