ble.com/Release-plugin-tagging-parent-of-trunk-tp4313642p5497781.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands,
Thanks for the replies Roland, it's much appreciated,
Here's some excerpts from the logs:
Here is a log with dryRun=false where you can see the copy command for the
tag using the project root instead of trunk. Also you can see that unlike
the other parts of the execution where the script starts b
That looks correct to me...
And thinking about it, tagBase can't be the reason for this, since the
tag is actually in the right place.
I'm afraid I don't know what else it could be... Maybe you could run a
release with debug-output and read something out of that? If not, you
could post it so al
The scm node seems correct, both and are
pointing at the trunk:
scm:svn:https://subversion.mycompany.com/java/project/trunk
I was under the impression that tagBase didn't need to be set if you were
using a standard trunk/branches/tags layout and would affect where the tag
was placed, not where
Are you sure that your and / are
correctly set?
On 19.04.2011 18:01, Brent Smith wrote:
> Hello,
>
> I'm running into an issue when I do a release:prepare on a multi-module
> project where the tagging phase is tagging the parent of the trunk. I found
> a bug report about something similar here:
Hello,
I'm running into an issue when I do a release:prepare on a multi-module
project where the tagging phase is tagging the parent of the trunk. I found
a bug report about something similar here:
http://jira.codehaus.org/browse/MRELEASE-562 however the workaround given in
a related ticket which
