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

Re: Feature request: Current checkout behaviour

From: Maik Hassel <hassel_at_simplyefficient.ca>
Date: 2005-11-13 19:10:21 CET

I am sorry to say this, but that these things are not supported by
subclipse is not true. We use Tortoise and the subversion command line
tools for exactly the scenarios described without problems. Checking out
a project into a src folder is tivial (change to the src folder,
checkout). Having the src folder as part of the src tree is an
unsatisfying workaround that would clash with other IDEs. We do this all
the time and it's just not supported by subclipse. Technically, the src
folder is part of the IDE's fodler structure and independant of the
project itself! So it should not be under version control.

Similar argument for the "single file" checkout. Subversion lets you set
directory level access privileges so users are only allowed to read or
write part of a source tree. No problem so far: Generate the "higer
levels" of the source tree by hand and check out the tree there.
Tortoise does this without problems and we use a simple wrapper script
that even automatizes the folder creation part. So again, this is very
much possible with subversion.

I think the problem boils down to:
a) Subclipse should allow you to check out a source tree in arbitrary
locations, not only the project root (the turtoise plugin for example
lets you do exactly this - problem solved)
b) Subclipse should be able to recognize if parts of a file tree are
under subversion control even if some other application checked it out.


Mark Phippard wrote:

>>a) Checking something out as a new java project when having separate
>>source and output folders. Problem: While eclipse creates the project
>>propperly with a src folder, the plugin checks out everything in the
>>main project folder, ignoring the src folder. This should be a very
>>basic functionality??? (I used "checkout as...")
>Your Eclipse project and the project in your repository have to have the
>same structure. If you have the src folder in your repository, then it
>works fine.
>>b) Some users check out only parts of a source tree. To illustarte the
>>problem, lets assume we check out only com/a/b/c/somefile.java. Due to
>>the package nature of java, the folder hirarchy HAS to be created
>Subversion does not support single-file checkouts and it has very little
>support for checking out a subset of a tree. You pretty much cannot do
>this with Subversion and therefore Subclipse.
>>Am I missing anything, am I doing something wrong or are there any plans
>>of fixing/implementing these features?
>The tree-based design of Subversion makes it a lot more picky about this
>stuff. Neither of these items could ever be implemented unless Subversion
>makes some major changes in its design.
>Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org

Simply Efficient - IT Services, Consulting, Training
"We Keep Our Promises"
Vancouver, BC
Phone: +1 604.315.8446
Fax  : +1 604.731.1147
Received on Mon Nov 14 05:10:21 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.