I am NOT an expert on this. I am good with code and have spent 8 hours
on this and my 2 cents on the situation...
The eclipse version control plugin support between M5 and M6 appears to
be radically refactored. Radical meaning they agile programmed it to
death ;-) probably a good thing in the long term but in the short term
it is a fair bit of work. I suspect that the differences between each
eclipse M# version will stabilize when 3.0 is released as a "Latest
Release" build as opposed to a 3.0 stream stable build. In essence the
m# releases are betas and it is difficult to keep up with the
refactoring joneses on the eclipse team.
A good way to test this theory are 1) see if anyone on this list cries
hogwash 2) to see if any other version control plugins NOT written by
the eclipse team are ready for M6 (I could not find a single one)
So I like many on this list would LOVE to be on the bleeding edge of
everything Subversion 0.36 and Eclipse M6.... What I am learning is
that you can only be on a few bleeding edges but can be on many trailing
edges ;-)
regards,
Glen
Domsch, Christian wrote:
>Hi all.
>
>I justed noticed, that you made a new binary for eclipse 2.1* compiled with
>subversion 0.35.1. Since I use Eclipse 3.0 M6 I wonder, if u will compile a
>version there, too. I hope someone will answer this quick, because we can
>only start to use subversion with a proper IDE support.
>
>Thanks in advance,
>
>Christian Domsch
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
Received on Thu Jan 29 00:32:28 2004