Re: java package

[John W. Eaton]

On  9-May-2012, Jordi Gutiérrez Hermoso wrote:

| Could I propose an alternative to making Java part of core? The
| problem is that installing packages from Octave Forge is a pain in the
| neck, right? So can't we fix that instead? We all mostly agree that
| there is a problem with the separation of Octave and Octave Forge, so
| if we bring them close together enough to the point where it's mostly
| painless to install, maintain, and develop packages, in a single
| unified way, can't we work on that instead?
| 
| I am very much not happy with the idea of making Java part of my
| regular Octave builds of which I do many per day, nor all of the cruft
| that comes with Java, and if I can avoid reading Java code, I would
| much prefer so. So for people like me who don't want to touch Java,
| can't we modularise and keep it modular?

I'm not proposing to make it a hard requirement to have Java installed
to be able to build Octave.  And even if you do have Java installed,
you could still avoid it by passing --without-java to configure.

jwe