Actually, I did declare it. You just didn't follow the link to the
changelog.
I just did not bother to recreate the changelog in the email.
You ALWAYS will need a new JavaSVN because their plugin extension works by
supplying their own version of the core plugin with a .1 version added to
the end so that Eclipse loads it instead of the one provided by Subclipse.
Of course, once we have JavaSVN as a clientAdapter choice this will all go
away.
Mark
Bill Wohler <wohler@newt.com> wrote on 04/08/2005 10:42:21 AM:
> Mark,
>
> You usually mentioned that an update requires an updated JavaSVN. Does
> you lack of mentioning it here imply that it is not required or that you
> forgot to mention it? ;-)
>
> In the future, it would alleviate this ambiguity to explicitly declare
> the necessity either way.
>
> Many thanks to both you and Alexander.
>
> --
> Bill Wohler <wohler_at_newt.com> http://www.newt.com/wohler/ GnuPG
ID:610BD9AD
> Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
> If you're passed on the right, you're in the wrong lane.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
_____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs.
>
_____________________________________________________________________________
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sat Apr 9 00:47:15 2005