RE: [Subclipse-users] How to make Subclipse aware that a project is SVN managed?

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 Subclipse.

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

…

  _____

De : johann.petrak@gmail.com [mailto:johann.petrak@gmail.com]
Envoyé : lundi 19 juin 2006 10:51
À : users@subclipse.tigris.org
Objet : [Subclipse-users] How to make Subclipse aware that a project is SVN
managed?

I have an *existing* (Java) project in Eclipse that has been created by
creating a Project from an existing Ant buildfile.

This project has been managed by svn already, so there are the .svn
directories.

However I only now installed Subclipse and it seems Subclipse does not
recognize that this project is managed by SVN (although all the information
is present in the .svn files).

I would have expected that this should be sufficient for Subclipse to
immediately let me do everything I did with command line subversion commands
before, but nothing of that sort happens.

So what does it need to make Subclipse aware of the fact that this project
is SVN managed?

Everything I tried yet either requires that I check out the module again
and/or that the project does not already exist as an Eclipse project.

I am pretty puzzled here -- in Netbeans, subversion information was shown as
soon as I installed the plugin without any additional intervention --
everything was taken from the files in the .svn directories, obviously.
Received on Mon Jun 19 11:25:17 2006