[jira] Commented: (MRELEASE-359) Release plugin depends on mvn being in the path of the shell that started the current build

["Rich Seller (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139561#action_139561 ] 

Rich Seller commented on MRELEASE-359:
--------------------------------------

The build now fails with a NPE because there is no default value for the mavenExecutorId, setting a default value on the parameter (as below) seems to address this

    /**
     * Role-hint of the {@link MavenExecutor} implementation to use.
     *
     * @parameter default-value="invoker"
     */
    protected String mavenExecutorId;

> Release plugin depends on mvn being in the path of the shell that started the current build
> -------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-359
>                 URL: http://jira.codehaus.org/browse/MRELEASE-359
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-7
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Critical
>             Fix For: 2.0-beta-8
>
>
> It's impossible to run a project release from an environment that uses maven without putting it in the path environment variable. This causes problems with build servers like Hudson, where you want to be able to configure on a project-by-project basis the version of Maven being used. The only alternative is to choose a version of Maven to put into the shell environment PATH used to start the appserver.

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