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

Göran Uddeborg updated MRELEASE-593:
------------------------------------

    Attachment: testcase.tar.bz2

Sorry, sent the wrong test case.  Here is the one I referred to in the 
description.

> Command line definitions are not available during the entire release process
> ----------------------------------------------------------------------------
>
>                 Key: MRELEASE-593
>                 URL: http://jira.codehaus.org/browse/MRELEASE-593
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-8
>         Environment: RHEL 5
> Maven 2.2.1
> Java 1.6.0_21
>            Reporter: Göran Uddeborg
>         Attachments: log, testcase.tar.bz2, testcase.tar.bz2
>
>
> In our build envioronment all projects import a dependency management 
> project.  The version of the dependency management project is controlled on 
> the command line.  Apparently, this breaks the maven plugin.  It appears as 
> if it works part of the way, but fails later.
> I include a test case consisting of three projects:
> * _cepa_ is a project to depend on.  It doesn't really contain anything.
> * _apa_ is a project to import as a dependency management.  It specifies 
> which version of _cepa_ to use.
> * _bepa_ is the project I want to release.  It depends on _cepa_, but doesn't 
> specify the version.  Instead it imports _apa_ for that.
> To reproduce:
> # (cd cepa; mvn install)
> # (cd apa; mvn install)
> # (cd bepa; mvn -Dbaseline=1.0.0 release:prepare)
> The last step starts ok, asking for release numbers and tag name.  But then 
> it starts to look for apa without "baseline" expanded, which of course fails. 
>  I include the complete log.
> Other commands work fine in _bepa_.  _mvn -Dbaseline=1.0.0 install_ does what 
> I expect, for example.  Only the release plugin breaks.  (So far.)

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


Reply via email to