[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: subclipse not recognizing managed project FIXED (Was: [ANN] JavaSVN v0.8.8 - broke my working copies?)

From: Ian Brockbank <Ian.Brockbank_at_wolfsonmicro.com>
Date: 2005-04-22 12:56:57 CEST

Hi Hugo,

> While I'm typing this mail I realize Ian's tip about capitalization.
> workspace on D:\ is in D:\Code\Java\eclipse\workspace (note the
> C and J). So I tried again checking out in D:\test. That works. Check
> out again in D:\Test --> Fail!

That's exactly what I was talking about. You can fix it by deleting the
project from Eclipse and re-importing it. Before you accept the import
path, hit "Browse" - that will make sure the capitalisation is correct.
You can then right-click on the project and go to Team-Share Project...
Subclipse should recognise it's already SVN and offer to check the
repository. Once you have accepted this, all should work again.

> So is this a known subclipse issue or is it a subversion issue? Ian is

> this what you meant? I think I did not get the hint entirely when you
> mentioned it. Thanks anyway for that. So I guess my workaround will be

> to put the workspace in a different path. Still I don't get why it has

> worked before. Anyway, I'm happy that it does now :)

You don't need to put the workspace in a different path - you just need
make sure that Eclipse has the capitalisation that matches the
Follow the steps above to fix it.

I first reported this in the late 0.9.teens.


Ian Brockbank
Applications Software Team Leader
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001
Received on Fri Apr 22 20:56:57 2005

This is an archived mail posted to the Subclipse Users mailing list.