Re: The problem of core classes for Java compilers (Was: Bug#44462: jikes: jikes does not find core classes
Make a file "/usr/share/java/core-compiler-classes.jar" that is managed
via the alternatives mechanism. Some other name could be used, but this
would suffice. There could be a virtual package of the same name which
is provided by the debs which supply said .jar.
On another note, I think that this whole /usr/share/java/repository thing
may create more problems than it solves. I'm not entirely sure about that,
but I kind of feel that way.
On Wed, Sep 08, 1999 at 03:14:18PM +0200, Stephane Bortzmeyer wrote:
> [It may be a good idea to copy important messages to 44462@bugs.debian.org
> since this problem is logged as a jikes bug.]
>
> Jikes has a problem with core classes. It can use those of the JDK or those of
> kaffe (which allows it to stay free) but is is necessary to tell it where to
> find them.
>
> Which means you cannot compile even the smallest program without setting
> CLASSPATH to indicate where it can find core classes.
> <http://www.research.ibm.com/jikes/jikes.htm#jikespath> directly violates
> Debian policy about environment variables.
>
> Mike Goldman, jikes' maintainer, suggests that Java virtual machines put the
> core classes in the Java Repository, /usr/share/java/repository. That way,
> jikes will find them.
>
> This was discussed at the beginning of the talk about the Java policy and
> dismissed because of the risk to have two VMs trying to put conflicting
> java.lang.* into /usr/share/java/repository.
>
> So, the policy says:
>
> > The problem of Java core classes is put on hold. In the mean time,
> > Java virtual machines are requested to come with their own core classes.
> > (Or to depends on another VM, like jikes does.)
>
> Any suggestion on the best way to solve the problem?
>
> 1) Follows Mike's suggestion, which would need to change the policy, to change the VM a bit and to find a way to deal with the conflict mentioned above.
>
> 2) Make a package of core classes (may be from kaffe's Klasses.jar) and let jikes depend on it. If this package comes from kaffe's classes, the best thing would be to have kaffe sources build two packages.
>
> 3) Integrate core classes (may be from kaffe or from GNU's classpath) into jikes. It would mean incorporating it upstream.
>
>
>
> --
> To UNSUBSCRIBE, email to debian-java-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
___________________________________________________________________
Ean Schuessler Freak
Novare International Inc. Freak Central
--- Some or all of the above signature may be a joke
Reply to: