To quote this announcement:
==
One of the most important problems preventing a general Java community
migration from CVS to Subversion is the absence of Subversion support
in development tools. Because the most popular Eclipse development
platform doesn't support Subversion, it's pretty complicated to work
together with Eclipse and external Subversion client tools. Besides
Subversion, there is also another well-known Eclipse plug-in available
for the community named Subclipse, which provides access to
Subversion. Internal structures of Subversion and Subclipse are
different because of different history of both projects.
==
Is it just me, or did the author of this not fully understand what he
was talking about? Subversion, isn't an eclipse plug-in, that's what
subclipse is for. And how is using subclipse any more complicated
than using the inbuilt CVS? Duh.
According to the timescales, this won't get off the drawing board for
another 6 months, by which time subclipse will be the de-facto
standard.
On 30/06/06, Markus KARG <markus.karg@quipsy.de> wrote:
> Why that?
> Why not just contributing Subclipse to the Eclipse Project?
> Do some people always need to reinvent the wheel?
>
> Vairoj A. schrieb:
>
> > Hi,
> >
> > Have anyone heard of this news?
> > http://www.eclipse.org/proposals/subversive/
> >
> > How does this impact on Subclipse development?
> >
> > Cheers,
> > Vairoj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> > For additional commands, e-mail: users-help@subclipse.tigris.org
> >
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jun 30 09:19:28 2006