Thanks Stephen. See comments below... On Tue, Oct 19, 2010 at 4:16 PM, Stephen Connolly <[email protected]> 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 shouldn't use the path from the working copy URL with the protocol from the pom scm connection. > 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 read-write) Unfortunately, half our developers are using http:// and the other half are using svn+ssh://, and I don't see that changing. > when making a release you really should be using the connection > specified in the devConnection part of the scm section. Sounds kinda like an excuse :) How do you handle this scenario in general? I'm sure many companies out there allow more than one way to access SVN. So you have to make a rule that only developers who check out code with a specific protocol can do releases? > for svn, setting remote tagging to true should work around your issue > somewhat. Yep, sure enough it that did the trick. Thanks for that workaround! But anyway, should I still submit a bug? I don't know if it is the release plugin or SCM plugin at fault though... 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 like that would really simplify things, and I don't see any downsides. Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
