[ 
https://jira.codehaus.org/browse/MVERSIONS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285596#comment-285596
 ] 

Stephen Connolly commented on MVERSIONS-150:
--------------------------------------------

Do you want to lather, rince and repeat?
                
> resolve-ranges fails for multi-module project with inter-module dependencies 
> w/o doing mvn install
> --------------------------------------------------------------------------------------------------
>
>                 Key: MVERSIONS-150
>                 URL: https://jira.codehaus.org/browse/MVERSIONS-150
>             Project: Maven 2.x Versions Plugin
>          Issue Type: Bug
>         Environment: Maven 2/3
>            Reporter: Eric Pabst
>         Attachments: MVERSIONS-150.diff
>
>
> I have a multi-module project that has version ranges for some of its 
> dependencies.  Some of the modules depend on some of the other modules (not a 
> version range).  When I run versions:resolve-ranges, it fails if I haven't 
> done a mvn install first.  Doing the mvn install first is not desired because 
> I want to do the install after resolve-ranges finishes so that the pom.xml's 
> are installed with the resolutions.

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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to