Re: [Subclipse-users] Upgrade to 1.8.1 Invalid Character Exception

On Mon, Oct 24, 2011 at 5:02 AM, Wolfgang Pinitsch <
wolfgang.pinitsch_at_hyperwave.com> wrote:

> I tried to upgrade a „large“ eclipse svn project (worked really good with
> subclipse 1.6), but the upgrade failed with 1.7/8 and failed again with
> 1.8.1.
>

The work is all done by SVN, so there is nothing we can do in Subclipse to
help. There have been hundreds of these reports on the SVN mailing list.
 These are legitimate forms of corruption in your 1.6 WC that SVN is
reporting. One of the things I believe they fixed in 1.7.1 was to report
more information. For example, if you at least knew which file was the
problem you could do something like:

$ svn up --set-depth=empty parentFolder

This would change the parent folder to not have any files in it. You could
then run svn upgrade successfully and run this command to put the files
back:

$ svn up --set-depth=infinity parentFolder

Short of that, I think you have to do a fresh checkout using 1.7.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2862374
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].