maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MRELEASE-509) Release dependencies before releasing the projects
Date Sat, 18 Sep 2010 03:50:32 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed MRELEASE-509.
---------------------------------

    Resolution: Won't Fix
      Assignee: Brett Porter

I think this over-reaches the scope of the release plugin. It might be best to consider a
separate plugin to do this.

> Release dependencies before releasing the projects 
> ---------------------------------------------------
>
>                 Key: MRELEASE-509
>                 URL: http://jira.codehaus.org/browse/MRELEASE-509
>             Project: Maven 2.x Release Plugin
>          Issue Type: Wish
>            Reporter: Mohammad Norouzi
>            Assignee: Brett Porter
>
> Consider we have project A which is dependent to B and C with SNAPSHOT version. then
what if the project version manager was able to run the command with an option and the plugin
first checks out all the snapshot versions and creates a release version for each and then
create a release version for project which this plugin is fired and update all the pom files.

-- 
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

        

Mime
View raw message