Java Mailing List Archive

http://www.java2.5341.com/

Home » issues.maven »

[jira] Updated: (MRELEASE-3) release:prepare should not require
multimodule artifacts to be in the local repository

Jan Bartel (JIRA)

2008-10-27


Author LoginPost Reply

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

Olivier Lamy updated MRELEASE-3:
--------------------------------

  Fix Version/s:   (was: 2.0-beta-8)
            2.0-beta-9

IMHO it's more a MNG issue.
If you run your project with clean verify, with a clean repo and no modules deployed as a SNAPSHOT, it will fail too.
SO use -DpreparationGoals="clean install"

> release:prepare should not require multimodule artifacts to be in the local repository
> --------------------------------------------------------------------------------------
>
>           Key: MRELEASE-3
>           URL: http://jira.codehaus.org/browse/MRELEASE-3
>         Project: Maven 2.x Release Plugin
>       Issue Type: Bug
>        Reporter: John Casey
>        Assignee: Emmanuel Venisse
>         Fix For: 2.0-beta-9
>
>
> Currently, if you try to run release:prepare on a multimodule project after removing any of that build's artifacts from the local repository, it will fail. Investigate why release:prepare needs the multimodule artifacts installed in the local repository before it can succeed.
> To reproduce, comment the following line in it2002/test.sh:
> mvn clean install
> NOTE: This may have to do with the version resolution code, which is used to resolve SNAPSHOT versions.

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

   
©2008 java2.5341.com - Jax Systems, LLC, U.S.A.