Re: svn commit: r511833 - /incubator/servicemix/trunk/pom.xml
The problem seems due to a failure in the merge/switch. The error message is a bit obtuse, but seems to relate to switching to/from a folder which doesn't exist. It might be worth trying to back out those changes and apply them individually to see which breaks? -- Terry Cox Meta-Concepts Ltd
Re: svn commit: r511833 - /incubator/servicemix/trunk/pom.xml
Yeah, but I have no admin rights there afaik, and I have no idea who setup that :-( On 2/26/07, Terry Cox <[EMAIL PROTECTED]> wrote: > Author: gnodet Date: Mon Feb 26 06:53:33 2007 New Revision: 511833 > URL: http://svn.apache.org/viewvc?view=rev&rev=511833 Log: Remove > continuum notifier I guess you are probably on this already, but just in case, changing the pom hasn't fixed the problem because it's a svn issue: Provider message: The svn command failed. Command output: --- svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within Continuum can't get a new copy of the source including that pom change, so it is still using the original copy. You may have to stop continuum and manually clean its build folder first to see if the problem is there or in svn. Cheers, -- Terry Cox Meta-Concepts Ltd 0788 1920512 -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: svn commit: r511833 - /incubator/servicemix/trunk/pom.xml
Author: gnodet Date: Mon Feb 26 06:53:33 2007 New Revision: 511833 URL: http://svn.apache.org/viewvc?view=rev&rev=511833 Log: Remove continuum notifier I guess you are probably on this already, but just in case, changing the pom hasn't fixed the problem because it's a svn issue: Provider message: The svn command failed. Command output: --- svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within Continuum can't get a new copy of the source including that pom change, so it is still using the original copy. You may have to stop continuum and manually clean its build folder first to see if the problem is there or in svn. Cheers, -- Terry Cox Meta-Concepts Ltd 0788 1920512
