Re: Debian & Java
Paul Reavis <email@example.com> writes:
> >I am doing some Java development and I am dealing with a few issues.
> >Is someone working on policy for how Java apps and libraries get
> >installed in Debian (e.g. how would a library add to a global
> >classpath so that one can use it)?
> No, but I have some very nice scripties that I wrote to handle just that
> issue. I'm hoping to package up something this month; currently
> code-named lava (pending checking for name conflicts with other
> Basically, here's the gist of my current scheme:
> Installed java applications and libraries:
> * Distributed with OS -> /usr/lib/java/*.jar
> * Local system-wide -> /usr/local/lib/java/*.jar
> * User -> ~/lib/java/*.jar
> A perl script, currently called "lava", goes through these dirs in order
> (I may replace with an explicit path), builds a CLASSPATH argument and
> passes it off to "java" via the -classpath switch.
Hmm. I'm not quite sure the mechanics of this are exactly what we
need. Maybe I'm confused. Instead of running 'java' or 'jre' or
'appletviewer', one would run lava?
It might be better to add this sort of cool hack (no offense) into the
actual java wrapper scripts (i.e., /usr/bin/appletviewer), for the
interests of interoperability.
> In any case, I volunteer to help with a Debian-Java standardization
All power to you. I propose you write up a little subpolicy and work
with the jdk and kaffe maintainers to get it implemented, and package
up the policy and any code.
Then I could ship the java stuff like SAX and IBM's xml4j.
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com