You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:46:21 UTC

[jira] [Closed] (MRELEASE-690) Check the repository if the version has already been released before

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

Michael Osipov closed MRELEASE-690.
-----------------------------------
    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.

> Check the repository if the version has already been released before
> --------------------------------------------------------------------
>
>                 Key: MRELEASE-690
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-690
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>          Components: prepare
>            Reporter: Christopher Cudennec
>
> The plugin does not check the repository if the version to be released is already in the repository. Instead you get a couple of SCM changes and a failed build.
> Each module of the project must be checked to prevent that some modules were released and some were not.
> This feature would really add to the robustness and quality of the plugin. At the moment the plugin lets you deal with the mess in case anything went wrong.
> In my opinion this issue is connected to MRELEASE-572 / MRELEASE-165 (checking if the tag already exists in the SCM).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)