Ok, can you see any other alternative to what I'm proposing? Do you see any
obvious flaws to my thinking in the way I have my projects laid out?
I'm open to suggestions, my main concern is that we have a number of
projects that are shared among many programs, and I wanted to devise a
layout where they are all still stored in the same repository to allow the
kind of tagging I've described (as I said, I came from the CVS world in this
regard).
If I were to make a patch to Subclipse to perform this, what is the process
to get it incorporated, or would it probably be rejected?
I would envision it working just as the tag functionality does now, except
that there might be a warning on the dialog indicating this is a multi
operation exercise and that it would not ba an atomic commit.
I just get the feeling I might have something laid out wrong if this is not
a feature that has been proposed before, since it is so common in the CVS
world with Eclipse projects (that I've seen).
On 12/6/05, Mark Phippard <markp@softlanding.com> wrote:
>
> Matthew Wheaton <mdwheaton@gmail.com> wrote on 12/06/2005 02:35:55 PM:
>
> > Totally understood. I know that it would not be an atomic commit, but
> the
> > Subclipse plugin (or patch to it), could do what I described on each URL
>
> > (selected project, or folder), could it not, instead of repeating the
> > operation for each folder ?
>
> Probably. I am not sure it is something I would want to do though.
>
> Mark
>
>
>
> _____________________________________________________________________________
> 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
>
>
Received on Wed Dec 7 07:02:42 2005