You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/02/28 18:48:03 UTC

[jira] (MRELEASE-310) ForkedMavenExecutor assumes mvn is on command-line path

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

Robert Scholte closed MRELEASE-310.
-----------------------------------

    Resolution: Duplicate

Duplicate of MRELEASE-428, which was already fixed in version 2.0-beta-8
                
> ForkedMavenExecutor assumes mvn is on command-line path
> -------------------------------------------------------
>
>                 Key: MRELEASE-310
>                 URL: https://jira.codehaus.org/browse/MRELEASE-310
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform, prepare, stage
>    Affects Versions: 2.0-beta-7
>            Reporter: Brian Jackson
>         Attachments: ForkedMavenExecutor.patch
>
>
> The ForkedMavenExecutor assumes the mvn executable is on the command-line path.  This will cause the release goals to fail if mvn is run from an explicit path and the PATH environment variable has not be set to contain a mvn executable.  More dangerously though is the case where the release goal is started with an explicit mvn executable of one version (for instance 2.0.8) but a different version of the mvn executable is available on the PATH.  The forked processes will run a different version of Maven2 that the parent process.

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