Maven 2.x Release Plugin

release:perform does not take the settings specified by the -s option

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0-beta-7
  • Fix Version/s: None
  • Component/s: perform
  • Labels:
    None
  • Number of attachments :
    0

Description

  1. mvn -s <some.custom.settings.xml> release:perform

does not take the settings.

If we copy the same to - ~/.m2/settings.xml

  1. mvn release:perform

works fine.

Something does not add up.

Issue Links

This issue duplicates:
MRELEASE-577 release:prepare does not pass argument "--settings" with current settings.xml to inner maven Critical Closed

Activity

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

<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-7</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-utils</artifactId>
<version>1.5.6</version>
</dependency>
</dependencies>

being used.

<prerequisites>
<maven>2.0.9</maven>
</prerequisites>

Show
Kay Kay added a comment - <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.0-beta-7</version> <dependencies> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-provider-gitexe</artifactId> <version>1.3</version> </dependency> <dependency> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-utils</artifactId> <version>1.5.6</version> </dependency> </dependencies> being used. <prerequisites> <maven>2.0.9</maven> </prerequisites>
Hide
Permalink
Christoph Kutzinski added a comment -

I've just confirmed that it still happens with release-plugin 2.1.
Another workaround is to append -Darguments="-s<my_settings_file>" to the release:perform call. E.g.

mvn -s<my_settings_file> release:prepare release:perform -Darguments="-s<my_settings_file>"

See also http://maven.40175.n5.nabble.com/mvn-release-perform-does-not-honor-servers-server-in-alternate-settings-location-td70612.html

Show
Christoph Kutzinski added a comment - I've just confirmed that it still happens with release-plugin 2.1. Another workaround is to append -Darguments="-s<my_settings_file>" to the release:perform call. E.g. mvn -s<my_settings_file> release:prepare release:perform -Darguments="-s<my_settings_file>" See also http://maven.40175.n5.nabble.com/mvn-release-perform-does-not-honor-servers-server-in-alternate-settings-location-td70612.html
Hide
Permalink
Stephen Connolly added a comment -

Closing this in favour of MRELEASE-577 as that has the suggestions for how to fix

Show
Stephen Connolly added a comment - Closing this in favour of MRELEASE-577 as that has the suggestions for how to fix

People

  • Assignee:
    Unassigned
    Reporter:
    Kay Kay
Vote (1)
Watch (1)

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.