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 05:38:27 UTC
[jira] Created: (MRELEASE-364) release:prepare fails with simple
pom
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: 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
[jira] Updated: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gilbert updated MRELEASE-364:
-----------------------------------
Attachment: invoker_executor_log.txt
invoker_executor_pom.xml
pom and log file for run with "invoker" executorId specified
> 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, invoker_executor_log.txt, invoker_executor_pom.xml, 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
[jira] Issue Comment Edited: (MRELEASE-364) release:prepare fails
with simple pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142895#action_142895 ]
Benjamin Bentmann commented on MRELEASE-364:
--------------------------------------------
bq. so I assumed you wanted a mvn run with "-X" even though you did not specify
Oh yes, I forgot the most important part of the story. Thanks a lot for the logs!
bq. I've gotten around the NPE using the "invoker" mavenExecutor by modifying the code to handle the null string.
Yep, that's it. I already have a concrete idea about the other issue with the NoSucheMethodError, too.
bq. I have a bizarre error about an invalid task "and"
I bet this is from
{noformat}
Building Maven user-level plugin registry from: 'C:\Documents and Settings\gilberts2\.m2\plugin-registry.xml'
{noformat}
i.e. it doesn't properly handle spaces...
> 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
[jira] Updated: (MRELEASE-364) InvokerMavenExecutor fails with NPE
if additional arguments are not set
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MRELEASE-364:
---------------------------------------
Summary: InvokerMavenExecutor fails with NPE if additional arguments are not set (was: release:prepare fails with simple pom)
> 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
> 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
[jira] Closed: (MRELEASE-364) InvokerMavenExecutor fails with NPE
if additional arguments are not set
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MRELEASE-364.
--------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.0-beta-8
Applied patch to fix NPE in [r679172|http://svn.apache.org/viewvc?view=rev&revision=679172], thanks Steve!
As for the remaining issues, I opened distinct JIRA ticket: MRELEASE-365 and MRELEASE-366.
> 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
[jira] Commented: (MRELEASE-364) InvokerMavenExecutor fails with
NPE if additional arguments are not set
Posted by "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
[jira] Updated: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gilbert updated MRELEASE-364:
-----------------------------------
Attachment: invalid_task_and_log.txt
Now that I am past the NPE, I have a bizarre error about an invalid task "and" apparently when the child maven process is executed:
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Invalid task 'and': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO] [INFO] ------------------------------------------------------------------------
I've attached a full debug log.
> 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
[jira] Commented: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142859#action_142859 ]
Benjamin Bentmann commented on MRELEASE-364:
--------------------------------------------
Steve, this looks like a duplicate of MRELEASE-360 which has just been fixed. Can you check if the new snapshot works for you? Otherwise, please attach a full debug log, i.e. run
{noformat}
mvn release:prepare -DdryRun=true > debug.log
{noformat}
to further investigate your issue. Also, the configurations for {{mavenExecutorId}} you quoted look good so I am not sure why these didn't work for you.
> 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: 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
[jira] Updated: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gilbert updated MRELEASE-364:
-----------------------------------
Attachment: forkedpath_executor_log.txt
forkedpath_executor_pom.xml
pom and log file for run with "forked-path" executorId specified
> 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, invoker_executor_log.txt, invoker_executor_pom.xml, 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
[jira] Commented: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gilbert updated MRELEASE-364:
-----------------------------------
Attachment: no_executor_log.txt
no_executor_pom.xml
pom and log file for run with no executorId specified
> 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
[jira] Updated: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Gilbert updated MRELEASE-364:
-----------------------------------
Attachment: invokermavenexecutor_null_pointer_exception.patch
I've gotten around the NPE using the "invoker" mavenExecutor by modifying the code to handle the null string.
I've attached a patch.
> 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, 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
[jira] Issue Comment Edited: (MRELEASE-364) release:prepare fails
with simple pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ 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:17 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 {noformat}-npr{noformat} 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 "{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.
> 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
[jira] Commented: (MRELEASE-364) release:prepare fails with simple
pom
Posted by "Steve Gilbert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142922#action_142922 ]
Steve Gilbert commented on MRELEASE-364:
----------------------------------------
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