> Ultimately it comes down to developer support. There would have to be
> someone willing to do the work. IMO, you would never see support for
> Synch in 2.x, but there are certainly other improvements that could have
> been made.
What are some of these improvements you can think of, off the top of
your head? I'd like to get a feeling of the kinds of things that are
missing from the 2.x version of Subclipse, as I'm new to the plugin as
a whole.
> FWIW, I still use WSAD 5.x regularly with Subclipse without problem. I
> miss a lot of the 3.x features but I still have all of the essentials. I
> just use TortoiseSVN for what is missing.
Well, that is encouraging to hear. I was hoping that the 2.x version
of Subclipse wouldn't have any glaring bugs and if you're using it
regularly, I'm sure any bugs it does have are easily ignored.
I was thinking along the same lines of using TortoiseSVN for any
missing features. Could you elaborate a little more on the types of
operations you have to resort to Tortoise to achieve? Just in my
initial investigation, I've come up with this scenario so far:
In lieu of a Synchronize feature in Sublipse for E2.x, at least being
able to bring up a status page which shows all outgoing as well as
potential incoming changes would be useful. This is analogous to using
"svn status --show-updates". Unfortunately, it looks like Subclipse
only has the command "Show pending operations" which is analogous to
"svn update". I found I was able to achieve the desired effect by
using "Check for Modifications" in TortoiseSVN, however, when when
the dialog is initially brought up, it only shows local modications
until you click the "Check Repository" button to get all remote changes.
Thanks for your help... I really want to make this work for us. I
don't think it'll be too difficult to convince them as long as I have
all the "less than ideal" scenarios documented and suffiiciently well
worked around.
G
Received on Tue Aug 23 04:35:54 2005