Out of curiosity - how is it possible to cut a release without a
settings.xml file? Don't you *always* need repository credentials? I
guess if your repository was accessed via file://...

Note - This isn't to suggest that this issue shouldn't be resolved.



On 4/26/10 8:30 AM, Baptiste MATHUS wrote:
> Hi all,
> 
> I've been hesitating about posting this to the user list, but since it's
> more related to maven3, I put it on the dev list as my very first message
> here :).
> If I should better have post on the "users", please let me know.
> 
> 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
> http://jira.codehaus.org/browse/MNG-4408)
> 
> I'm posting here because I don't really know where the bug belongs. Is it to
> be considered a mvn3 regression? A release-plugin bug? Something/somewhere
> else?
> I'll file an issue if necessary where it must be put.
> 
> Just let me know what you think.
> 
> Cheers
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to