maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MCHANGES-148) Add ability to pull from more than one Jira project and version
Date Sun, 06 Sep 2015 20:46:24 GMT

     [ https://issues.apache.org/jira/browse/MCHANGES-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MCHANGES-148.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Add ability to pull from more than one Jira project and version
> ---------------------------------------------------------------
>
>                 Key: MCHANGES-148
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-148
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message