You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2011/06/25 10:27:42 UTC

[jira] Commented: (MRELEASE-456) Resolving version during release:prepare of main

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

Brett Porter commented on MRELEASE-456:
---------------------------------------

Sounds like a bug in Maven 2.1.0. Does it work in Maven 2.2.1?

> Resolving version during release:prepare of main
> ------------------------------------------------
>
>                 Key: MRELEASE-456
>                 URL: https://jira.codehaus.org/browse/MRELEASE-456
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform, prepare
>    Affects Versions: 2.0-beta-8
>         Environment: Windows Vista(main release), Unix(other projects' build), Nexus Repository Manager,Maven2.1.0, Maven-release-plugin2.0-beta-8
>            Reporter: Puneet Sahani
>         Attachments: error.txt
>
>
> Hi,
> we have a main project(of type pom) containing DependencyMgmt section which lists all the projects and a version property pointing to SNAPSHOT by default and changed to a version range with the activation of a profile.
> All other projects have a concrete versioned 'main' as there parent.
> But from my local PC(Windows Vista), if i run release:prepare of the main project, while deploying the pom to Nexus, it resolves the tag to the SNAPSHOT dependency. Hence build during the patch/release is failing during dependency resolution as it tries to resolve SNAPSHOT dependency instead of resolving via the Version-Range.
> I switched back to Maven2.0.9 and it works fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira