[jira] Commented: (MRELEASE-134) Release prepare fails with version ranges

["David Hoffer (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94627 ] 

David Hoffer commented on MRELEASE-134:
---------------------------------------

Does anyone know when this will be resolved?  Also, it seems that all (most) other plug-ins have the same problem; I have observed this bug with the idea, assembly & dependency plug-in.  It seems troubling to me that so many plug-ins have this bug.  

What are the workarounds for this?  We are to the point of being forced to not use version ranges, but we don't want to do this because the practice works so well if it were not for the bug!

What are the options?
-	If you don't use version ranges, how can you get the same behavior?
-	Could this be fixed?  Where is the code that resolves version ranges?  Is this shared across all plug-in or does each implement this in their own way?


> Release prepare fails with version ranges
> -----------------------------------------
>
>                 Key: MRELEASE-134
>                 URL: http://jira.codehaus.org/browse/MRELEASE-134
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>            Reporter: Mike Perham
>
> {code}
> <version>[1.1.0,)</version>
> {code}
> This version range can resolve to the latest dev SNAPSHOT which causes the release plugin to fail due to a SNAPSHOT dependency.  The release plugin should check that the original version specification includes a non-SNAPSHOT version (1.1.0) and so can be released without harm.

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