[jira] Commented: (MRELEASE-364) InvokerMavenExecutor fails with NPE if additional arguments are not set

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

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

Benjamin Bentmann commented on MRELEASE-364:
--------------------------------------------

Steve, regarding the "and" task: It's actually the path to the local repository that causes problems. You could edit your personal {{settings.xml}} and move the repo to a path without spaces.

Also, the "forked-path" MavenExecutor is running again, so you could add "-DmavenExecutorId=forked-path" on the command line and try that instead of "invoker".

bq. The same is true for debug output-- the child process doesn't log at debug level when I pass "-X" on the command line.
Most (if not all) options from the command line are not passed to the child build. To do so, you need to use the parameter {{[arguments|http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#arguments]}} of the Release Plugin.

> InvokerMavenExecutor fails with NPE if additional arguments are not set
> -----------------------------------------------------------------------
>
>                 Key: MRELEASE-364
>                 URL: http://jira.codehaus.org/browse/MRELEASE-364
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-8
>            Reporter: Steve Gilbert
>            Assignee: Benjamin Bentmann
>            Priority: Blocker
>             Fix For: 2.0-beta-8
>
>         Attachments: forkedpath_executor_log.txt, forkedpath_executor_pom.xml, invalid_task_and_log.txt, invoker_executor_log.txt, invoker_executor_pom.xml, invokermavenexecutor_null_pointer_exception.patch, no_executor_log.txt, no_executor_pom.xml, pom.xml
>
>
> Attempting to perform a release:prepare fails with a simple pom:
> -bash-2.05b$ mvn  release:prepare -DdryRun=true
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Test POM
> [INFO]    task-segment: [release:prepare] (aggregator-style)
> [INFO] ------------------------------------------------------------------------
> [INFO] [release:prepare]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: svn --non-interactive status
> [INFO] Working directory: /home/gilberts2/dev/maven_release_test
> [INFO] Checking dependencies and plugins for snapshots ...
> This project relies on a SNAPSHOT of the release plugin. This may be necessary d
> uring testing.: Do you want to continue with the release? (yes/no) no: : yes
> What is the release version for "Test POM"? (srg:test-pom) 1.0: :
> What is SCM release tag or label for "Test POM"? (srg:test-pom) test-pom-1.0: :
> What is the new development version for "Test POM"? (srg:test-pom) 1.1-SNAPSHOT:
>  :
> [INFO] Transforming 'Test POM'...
> [INFO] Not generating release POMs
> [INFO] Executing preparation goals - since this is simulation mode it is running
>  against the original project, not the rewritten ones
> [INFO] Executing goals 'clean verify'...
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Cannot find Maven executor with id: null
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 11 seconds
> [INFO] Finished at: Tue Jul 22 23:34:07 EDT 2008
> [INFO] Final Memory: 22M/64M
> [INFO] ------------------------------------------------------------------------
> I attempted to set the mavenExecutorId to both:
>                 <configuration>
>                     <mavenExecutorId>forked-path</mavenExecutorId>
>                 </configuration>
> and
>                 <configuration>
>                   <mavenExecutorId>invoker</mavenExecutorId>
>                 </configuration>
> In both cases a NullPointerException was the result.
> The pom file is attached.

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