Maven 2.x Release Plugin

Release plugin depends on mvn being in the path of the shell that started the current build

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-7
  • Fix Version/s: 2.0-beta-8
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

It's impossible to run a project release from an environment that uses maven without putting it in the path environment variable. This causes problems with build servers like Hudson, where you want to be able to configure on a project-by-project basis the version of Maven being used. The only alternative is to choose a version of Maven to put into the shell environment PATH used to start the appserver.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

I've added a new maven executor that uses maven-invoker, along with some changes that allow more than just the settings to be passed through the plugin execution into the maven executor.

Show
John Casey added a comment - I've added a new maven executor that uses maven-invoker, along with some changes that allow more than just the settings to be passed through the plugin execution into the maven executor.
Hide
Permalink
Rich Seller added a comment -

The build now fails with a NPE because there is no default value for the mavenExecutorId, setting a default value on the parameter (as below) seems to address this

/**

  • Role-hint of the {@link MavenExecutor}

    implementation to use.
    *

  • @parameter default-value="invoker"
    */
    protected String mavenExecutorId;
Show
Rich Seller added a comment - The build now fails with a NPE because there is no default value for the mavenExecutorId, setting a default value on the parameter (as below) seems to address this /** Role-hint of the {@link MavenExecutor} implementation to use. * @parameter default-value="invoker" */ protected String mavenExecutorId;
Hide
Permalink
Frederic Tardif added a comment -

Do I understand that the mavenExecutorId could be a way that the release plugin runs without forking a maven to support it's integration when it is launched through the maven embedder?

Does not seems to work for me with through m2e using maven-release-plugin 2.0-beta-9

see: http://jira.codehaus.org/browse/MRELEASE-310

Show
Frederic Tardif added a comment - Do I understand that the mavenExecutorId could be a way that the release plugin runs without forking a maven to support it's integration when it is launched through the maven embedder? Does not seems to work for me with through m2e using maven-release-plugin 2.0-beta-9 see: http://jira.codehaus.org/browse/MRELEASE-310

People

  • Assignee:
    John Casey
    Reporter:
    John Casey
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: