You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steve Gilbert (JIRA)" <ji...@codehaus.org> on 2008/07/23 20:17:27 UTC

[jira] Issue Comment Edited: (MRELEASE-364) release:prepare fails with simple pom

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

agency23 edited comment on MRELEASE-364 at 7/23/08 1:16 PM:
-----------------------------------------------------------------

Excellent catch.  It has to be that.  I've gone back to Linux and with my patch in place to get past the NPE, I can now get through a prepare dry run.

I can't change my home directory on the PC, so I have no workaround on the PC.  I can't tell if the problem is in the release-manager/plugin code or somewhere else.  I tried to run with "{code}-npr{code}" but that did not help since the problem is occurring in the child maven process and the parent's options are not passed to it.  The same is true for debug output-- the child process doesn't log at debug level when I pass "-X" on the command line.


      was (Author: agency23):
    Excellent catch.  It has to be that.  I've gone back to Linux and with my patch in place to get past the NPE, I can now get through a prepare dry run.

I can't change my home directory on the PC, so I have no workaround on the PC.  I can't tell if the problem is in the release-manager/plugin code or somewhere else.  I tried to run with "-npr" but that did not help since the problem is occurring in the child maven process and the parent's options are not passed to it.  The same is true for debug output-- the child process doesn't log at debug level when I pass "-X" on the command line.

  
> release:prepare fails with simple pom
> -------------------------------------
>
>                 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
>            Priority: Blocker
>         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