Maven 2.x Release Plugin

Release plugin invoker loses interactive mode

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0-beta-8
  • Fix Version/s: None
  • Component/s: perform, prepare
  • Labels:
    None
  • Environment:
    Windows XP, Cygwin, Java 1.5.0_16
  • Number of attachments :
    0

Description

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.

Issue Links

This issue duplicates:
MRELEASE-263 Interactive plugins cannot work in forked executions Critical Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Bentmann added a comment -

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

<mavenExecutorId>forked-path</mavenExecutorId>
Show
Benjamin Bentmann added a comment - 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 
<mavenExecutorId>forked-path</mavenExecutorId>
Hide
Permalink
Mark Hobson added a comment -

Sounds about right, this was within a project that didn't lock down the plugin versions. Thanks for the clarification.

Show
Mark Hobson added a comment - Sounds about right, this was within a project that didn't lock down the plugin versions. Thanks for the clarification.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.