[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Java wrappers and java-common

Michael Koch wrote:
> On Fri, Jan 04, 2008 at 04:42:30PM +0100, Vincent Fourmond wrote:
> java-common in Ubuntu has another mechanism applied to it (but its
> unused currently). Perhaps its possible to merge stuff from that.

  If I read the code right, they just have a list of possible JAVA_HOME
in a configuration file, and they try them in turn. Pretty basic, no
means to look for swing/xml/sun's classes and so on. No lookup for jar
files neither.

> Gentoo has a mechanism that is more similar to yours. Can you pleas
> compare it with yours. Perhaps its also possible to re-use stuff.

  Actually, it looks similar, but it is based on a rather large python
program to find dependencies and a JVM able to run them. This apparently
relies on a database of the various jar's dependencies and requirements
in terms of JVM version and capacities. While this is definitely the way
to go, it is a much larger project than a simple shell script help.

> Before we move stuff into Debian java-common it should be completely
> working for most cases. 

  Do you mind me moving to the SVN of java-common, as I don't think it
is a good idea to go on in batik ? It wouldn't be installed if a new
version of java-common is necessary, it would only be present in the
source tarball. (but I understand if you don't like the idea).

> Otherwise stuff tends to get another nominal
> member. We have enough of them already.

  When it comes to a more usable state, I'll check with a fair number of
packages from the svn repository.



Vincent Fourmond, Debian Developer
-- pretty boring signature, isn't it ?

Reply to: