[
http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142871#action_142871
]
Steve Gilbert commented on MRELEASE-364:
----------------------------------------
I have tried again with the snapshot from a few hours ago and the results were
pretty much the same.
I ran three times: with no executorId specified, with "invoker" specified, and
with "forked-path". The first two (which I believe are the same now with the
default value of "invoker" in the latest check in) resulted in a
NullPointerException. The third (forked-path) resulted in a NoSuchMethodError.
Benjamin - in your comment you asked for "full debug log", so I assumed you
wanted a mvn run with "-X" even though you did not specify. That is how I ran.
I will attach my three log files and three pom files.
Note that I checked my pom changes into my svn repo before each run to avoid
any possiblity of the release plugin complaining about local changes. The logs
also show that I am in fact using the latest snapshots of maven-release-manager
and maven-release-plugin.
> 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: 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
