>>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.
> I miss the Eclipse 3.x commit and revert dialogs. The feature I miss the
> most is that you cannot just do Revert on the project or a folder.
Good thing for me is that no one is used to doing easy reverts anyway,
since they are coming from CVS. :-)
> None of the features related to branching (switch, merge, copy) exist in
> 2.x. Also there is no way to resolve a conflict from within Eclipse 2.x.
Branching isn't a problem, as our users aren't sophisticated enough to
do their own branching anyway, I'll be handling all of that and likely
to use the command line or Tortoise.
As for conflicts, I just noticed that issue a few minutes ago after
running some tests. I'm wondering if there's a way to take the output
of the conflict (the 3 files and the modified original file with the
diff output in it) and switch over to Tortoise to resolve the
conflict, or maybe just go to WinMerge. I'll have to play around with
it and see what Tortoise itself does to resolve conflicts.
>>"svn status --show-updates". Unfortunately, it looks like Subclipse
>>only has the command "Show pending operations" which is analogous to
>>"svn update".
> Show Pending Operations is svn status with the -u switch. It is your
> local status.
Well, I hope you're right and I've got something misconfigured. But
when I click on "Show pending operations", the SVN Console view shows
"svn status"... it doesn't use the -u switch and doesn't show any
remote status. That's at least what I'm seeing, let me know if it's
different for you.
> The latest version of TortoiseSVN will remember that setting. Personally,
> commit emails are enough for me to know what is incoming. I prefer to
> just use update and let Subversion auto-merge the code and create
> conflicts if there are any.
Well, I agree with you. Hopefully I can get people to break some
habits (essential to learning to use Subversion anyway)... As or
Tortoise remembering that setting, I'll have to look into that. I'm
running TortoiseSVN 1.2.1, Build 3895 which seems to be the latest
according to its update mechanism.
> So why are you stuck with WSAD? Licensing issues? I thought they had a
> reasonable upgrade path to RAD. Have you considered moving to more of an
> Eclipse-centric approach? The Eclipse WTP 0.7 milestone is fairly usable
> and is based on the WSAD code. There is also stuff like My Eclipse and
> others that have reasonable license terms.
Mark my friend.. I hope you never have to struggle with the issues I'm
dealing with at the moment. The reason I'm stuck on E2.x is because of
the Eclipse plugins in our product. They only run in E2.x and there
isn't a huge effort to port them to E3.x at the moment (mainly because
the customers we're selling to seem to be using WSAD 5.x). Regardless
of the reasons, I'm pushing to get our stuff ported to E3 ASAP, but
unfortunately, it's only being treated as a spare time/weekend project
at the moment.
I've recently downloaded WTP 0.7 and had the latest Subclipse running
in it. I try not to run that environment too much as it only serves to
remind me of all the incredible features I have to live without!
Wish me luck... Hopefully I can succeed in making the switch to
Subversion.
G
Received on Tue Aug 23 05:53:07 2005