On 6/19/06, Vincent Goude <email@example.com> wrote:
> I think the problem was already encountered by another user last month.
> He used the last version of TortoiseSVN to checkout a working copy then
> went to eclipse and imported the project but couldn't manage it with
> The reason was the new 1.3.2 subversion client library used by TortoiseSVN
> changed the files contained in the .svn from workingcopies thus making them
> incompatible with the old client library used by subclipse. The repository
> is still compatible with both.
> Might be the same problem there, whether the library used by Ant being
> 1.3.2 and Subclipse's libray being older or the other way round.
> Solution: checkout a new working with Subclipse
I have not used anything but command line svn for this ... the files in .svn
are not altered in any way.
Do you mean to say that this *should* work as expected, i.e. Subvclipse
should automatically recognize that the project is SVN managed?
Which library are you referring to here?
I would really like to avoid to re-checkout the working directory with
Subclipse, because it is rather large and contains a lot of of local-only
files which would not get re-created properly.
Received on Mon Jun 19 11:40:51 2006