[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

jni bindings

From: Torsten Curdt <tcurdt_at_managesoft.com>
Date: 2004-09-29 19:27:34 CEST

...although still some things were missing (compared to
the eclipse cvs client) subclipse was already a nice
piece of software. ...*was* because since the remove
of the jni bindings renders the plugin useless (for us)!

We tried to create the jni bindings ourselves but for
some reason it's still not working. Besides you don't
wanna put this burden onto each an every user of the
plugin! ...at least it's not that easy as stated on
the web site.

Bugging the package maintainer does not help much
for Debian due to the fact that all the dependencies
have to be inside the same section:

> the packages in _main_
> * must not require a package outside of _main_ for compilation
> or execution (thus, the package must not declare a "Depends",
> "Recommends", or "Build-Depends" relationship on a non-_main_
> package),

Since subversion is in main all dependencies have
to be in main. (note: of course there is no sun jdk
nor the blackdown) The only one that is in main is
jikes ...is it possible to build the jni bindings
with jikes and gnu classpath?

Besides updating svn-javahl.jar with the self-build
one needs to be done for each and every eclipse
plugin update (through the manager)

We went back using the svn command line because of
the current situation. I hope this is heard...


Received on Thu Sep 30 03:27:34 2004

This is an archived mail posted to the Subclipse Dev mailing list.