You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/02/14 23:15:02 UTC

[jira] (MRELEASE-598) Repeatedly prompt for same release/next development versions of snapshot dependencies in multi-module projects

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

Robert Scholte updated MRELEASE-598:
------------------------------------

    Component/s: prepare
    
> Repeatedly prompt for same release/next development versions of snapshot dependencies in multi-module projects
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-598
>                 URL: https://jira.codehaus.org/browse/MRELEASE-598
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0
>            Reporter: Marcus Linke
>
> When having a huge multi-module project where the same dependencies are used in various submodules, the plugin prompts repeatedly the next development version for the same artifact/version combination over and over again. This is really annoying especially when having many submodules.
>    
> The plugin should reuse dependency version mappings once entered by the user for all subsequent/dependent modules. So if it finds a
> unmapped snapshot artifact/classifier/version combination in a module it can prompt the user for it and
> reuse this mapping for the whole process without prompting again. This behavior should work for all usecases, shouln't it?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira