[
http://jira.codehaus.org/browse/MRELEASE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169277#action_169277
]
Benjamin Bentmann commented on MRELEASE-424:
--------------------------------------------
The super POM shipped with 2.0.9 declares version 2.0-beta-7 of the Release
Plugin, whereas the super POM in 2.0.10 uses 2.0-beta-8. I assume that's the
reason why the Maven version makes a difference for you.
As of version 2.0-beta-8 of the Release Plugin, it uses the maven-invoker by
default. You can still get the old way of calling/forking Maven via the plugin
parameter
{code:xml}
<mavenExecutorId>forked-path</mavenExecutorId>
{code}
> Release plugin invoker loses interactive mode
> ---------------------------------------------
>
> Key: MRELEASE-424
> URL: http://jira.codehaus.org/browse/MRELEASE-424
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0-beta-8
> Environment: Windows XP, Cygwin, Java 1.5.0_16
> Reporter: Mark Hobson
>
> Trying to release a project using Maven 2.0.10 and get the following warning:
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker instance.
> This can be a problem when deployment requires interactivity due to SVN
> certificates, etc. I retried under 2.0.9 and it works as expected.
--
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
