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

[Subclipse-users] General Subclipse Usage Question

From: etornick <etornick_at_comcast.net>
Date: 2006-02-16 19:38:50 CET

We are thinking about using subclipse for a large project. This project will
have many developers, and some will be coming on board as newbies.
Additionally we are thinking of having a release manager be a coordinator of
the creation of the branches and tags.

For the most part, the developers will be working off the trunk until we
start gettting into more formal release procedures, then people might be
assigned to work on a branch for a specific maintenance release etc...

What concerns me is that it seems incredibly easy to go into the repository
view and select a folder (like the branches folder - (using the suggested
subversion folder layouts of branches - tags - trunk....)) and right click
and delete!!! You could blow away 50 branches this way!

I experimented with this a bit and it really did the delete from the
"eclipse perspective". The project in another eclipse workspace seemed to be
orphaned because when I tried a team->synchronize it said there was nothing
to synchronize with.

I figured there must be a way to control this so that certain people could
be restricted to doing certain operations and it seems like the "hooks" were
the only way.

Any ideas/thoughts on how to deal with this issue would be greatly


View this message in context: http://www.nabble.com/General-Subclipse-Usage-Question-t1136098.html#a2975933
Sent from the subclipse - users forum at Nabble.com.
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 16 19:42:44 2006

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.