2010/4/26 Benjamin Bentmann
> Baptiste MATHUS wrote:
>
> 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.
>>
>
> As you a
Ah. I forgot about wagon-svn. Thanks for the clarification.
Baptiste MATHUS wrote:
Hi,
Well, no. Using SVN, the credentials are stored externally. Or you can even
give them on the command line (-Duser/password).
And btw, we're using svn:// protocol.
Cheers
2010/4/26 Justin Edelson
Out o
Hi,
Well, no. Using SVN, the credentials are stored externally. Or you can even
give them on the command line (-Duser/password).
And btw, we're using svn:// protocol.
Cheers
2010/4/26 Justin Edelson
> Out of curiosity - how is it possible to cut a release without a
> settings.xml file? Don't y
Baptiste MATHUS wrote:
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.
As you already pointed out, the validation of the -s argume
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 wrot
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
