A few people (myself, and Julien to some degree, at least) have had
problems with Eclipse randomly losing the subversive association
between projects and svn, so that they would have to be checked out
again from Eclipse. Or the fact that when trying to re-enable svn for
a project, we would have to fill all information by hand instead of
having subversive autodetect all the settings.
The reason behind these problems is the use of a command-line svn
1.3. Between 1.2 and 1.3, there was a subtle change to the the format
of a file under .svn which made subversive's embedded JavaSVN puke
and fail to recognize a directory as svn-enabled if you manipulated
the sources from the command line svn.
Solutions:
- do not use command-line svn >= 1.3
- use recent's Subversive possibility of using a JavaHL library for
svn that uses the plaform's native svn libraries (needs -
Djava.library.path=/usr/lib or -Djava.library.path=/usr/local/lib
added to eclipse's eclipse.ini)
- upgrade to the latest Subversive 1.1.0 M9, which embeds JavaSVN
1.0.4 who understands svn 1.3
http://www.polarion.org/projects/subversive/download/1.1/update-site/
http://www.polarion.org/index.php?page=download&project=subversive
The latter is obviously the simplest.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
