Probably something went wrong during the copy process and you have old .svn
directories in the structure.
Check the content of the files in the .svn directory in
trinidad-1.0.10/trinidad-api and check if the url points to the correct svn
path and not to the trunk or any other tag path.
Ciao,
On Tue, Nov 11, 2008 at 1:18 PM, Simon Kitching [EMAIL PROTECTED] wrote:
Another good reason not to use maven-release-plugin :-)
:-) actually, Cagatay just said the same on IM.
yeah, it's funny that the release-plugin has a bug when preparing a release.
-M
Matthias Wessendorf schrieb:
http://jira.codehaus.org/browse/SCM-406
On Tue, Nov 11, 2008 at 12:40 PM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Probably something went wrong during the copy process and you have old .svn
directories in the structure.
Check the content of the files in the .svn directory in
Another good reason not to use maven-release-plugin :-)
Matthias Wessendorf schrieb:
http://jira.codehaus.org/browse/SCM-406
On Tue, Nov 11, 2008 at 12:40 PM, Mario Ivankovits [EMAIL PROTECTED] wrote:
Probably something went wrong during the copy process and you have old .svn
