"Alexander Kitaev" <alex@tmate.org> wrote on 07/20/2005 10:46:42 AM:
> > I have already thought the same thing as I would ideally like
> > the version of JavaHL or JavaSVN to be separate from
> > Subclipse. So you could install a new version of
> > JavaHL/JavaSVN by installing a new plugin, independent of
> > Subclipse. An enormous problem that I see is that
> > svnClientAdapter is not an Eclipse plugin. We cannot just
> > hack it up as there are other projects (at least svnAnt) that
> > need it outside an Eclipse environment.
> >
> > I am not sure how we can solve that problem.
> Another option that we could consider (and one of the JavaSVN users
already
> asked for that) is to deploy JavaSVN the following way:
>
> javasvn-core.jar // includes javasvn implementation and JavaSVN API
> javasvn-javahl-replacement.jar // uses javasvn-core.jar and provides
JavaHL
> API along with org.tigris.subversion.javahl.SVNClient class that
"replaces"
> JavaHL one.
> javasvn-javahl-impl.jar // uses svnjavahl.jar, javasvn-core.jar and
provides
> org.tmatesoft.svn.core.client.JavaSVNClient class (that implements
> SVNClientInterface) but doesn't "replace" JavaHL SVNClient class.
>
> In this case svnClientAdapter implementation for JavaSVN (copy of
> jhlAdapter) will use JavaSVNClient class from JavaSVN namespace, not
> SVNClient, but everething else will remain the same (in case jhlAdapter
uses
> SVNClientInterface). What do you think on that?
That sounds very feasible. Is this something you have already done, or
are planning?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Jul 21 00:48:47 2005