The convention seems to be, and the one that I have followed in the
releases I have built, is that we create a tag for the release in the tags
folder. You should be able to checkout from the relevant tag such as:
http://svn.collab.net/repos/subclipse/tags/subclipse/subclipse-3-0.9.27/
For the most part, this is what you want. The problem is with
svnClientAdapter. Technically, that is a separate project from Subclipse,
and we just "consume" its libraries in Subclipse. So the tag we create for
Subclipse contains the JAR we used for svnClientAdapter, not the source.
If you examine the history for the JAR file in the project, I have been
trying to identify what revisions I have built the JAR file from.
Currently, when I just generate the JAR file using the Eclipse export
option. I just do not select the JavaSVN package or the test packages.
Once the JavaSVN stuff is ready I will start including those classes in the
JAR.
See:
http://svn.collab.net/viewcvs/subclipse/branches/subclipse-3/core/svnClientAdapter.jar?rev=1255&view=log
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon Feb 28 12:08:00 2005