On 19 October 2010 23:43, Phillip Hellewell ssh...@gmail.com wrote:
Thanks Stephen. See comments below...
On Tue, Oct 19, 2010 at 4:16 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I suspect that this is because you are not using remoteTagging=true
for your release, so it is
On Wed, Oct 20, 2010 at 12:29 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 19 October 2010 23:43, Phillip Hellewell ssh...@gmail.com wrote:
Also, what about my idea that the release plugin ought to just use the
working copy URL when an scm connection is not defined? Seems
On Tue, Oct 19, 2010 at 4:43 PM, Phillip Hellewell ssh...@gmail.com wrote:
But anyway, should I still submit a bug? I don't know if it is the
release plugin or SCM plugin at fault though...
FYI, I created this bug: http://jira.codehaus.org/browse/MRELEASE-609
Phillip
On Oct 20, 2010, at 12:57 PM, Phillip Hellewell ssh...@gmail.com wrote:
On Wed, Oct 20, 2010 at 12:29 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 19 October 2010 23:43, Phillip Hellewell ssh...@gmail.com wrote:
Also, what about my idea that the release plugin ought to
On Wed, Oct 20, 2010 at 11:16 AM, Justin Edelson
justinedel...@gmail.com wrote:
On Oct 20, 2010, at 12:57 PM, Phillip Hellewell ssh...@gmail.com wrote:
So how about a solution where you still have to tell it the SCM just
not the URL, e.g., if the connection could be set to like
scm:svn:infer.
Hi all,
Both of these point to the same place:
My working copy URL: svn+ssh://usern...@addev/svnrep/components/core/trunk
My SCM URL in the pom: scm:svn:http://addev/svn/components/core/trunk
I'm getting this error when release:prepare tries to create a tag:
svn: Server sent
I suspect that this is because you are not using remoteTagging=true
for your release, so it is trying to create the tag from the working
copy.
the pom is not really designed to handle more than two valid scm
connection urls (1 is the at least read-only url and the other dev
connection is at least
Thanks Stephen. See comments below...
On Tue, Oct 19, 2010 at 4:16 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I suspect that this is because you are not using remoteTagging=true
for your release, so it is trying to create the tag from the working
copy.
Ok, but it still
