[
http://jira.codehaus.org/browse/MRELEASE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MRELEASE-551.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.1
Assignee: Benjamin Bentmann
Made plugin more careful in
[r980883|http://svn.apache.org/viewvc?view=revision&revision=980883]. The other
half of this issues lies actually in the core of Maven 3 which supplies the
path to the non-existing file.
> Unable to release with maven 3 when having no $HOME/.m2/settings.xml
> --------------------------------------------------------------------
>
> Key: MRELEASE-551
> URL: http://jira.codehaus.org/browse/MRELEASE-551
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8, 2.0-beta-9, 2.0
> Reporter: Baptiste MATHUS
> Assignee: Benjamin Bentmann
> Fix For: 2.1
>
>
> I've recently tried to release a small remote-resources project, but couldn't
> do it with mvn3. After some look-up, it seems to be the result of several
> changes:
> * I don't have any $HOME/.m2/settings.xml (only the
> $M2_HOME/conf/settings.xml is present and configured).
> * From the 2.0-beta-8 of the release plugin, it now uses the -s option during
> the prepare phase
> * from the mvn3.0-alpha-3, maven now don't ignore silently the absence of a
> settings.xml file specified with the -s option (see MNG-4408)
> To reproduce, try to run release:prepare with mvn3 without having a user
> settings.xml.
> Let me know if you need more information.
> Cheers
--
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
