[Octave-bug-tracker] [bug #38060] Java package offers wrong advice for setting JAVA_HOME

[Philip Nienhuis]

Update of bug #38060 (project octave):

                  Status:               Postponed => Wont Fix               
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #4:

(Sorry I was away for a week)

There's a section mentioning JAVA_HOME in the wiki
(http://wiki.octave.org/Java_package#Make_sure_that_the_build_environment_is_configured_properly),
a bit geared toward the use of JAVA_HOME while installing the Java package.
Precisely what this bug report is all about.

When the Java OF package got absorbed in core Octave, this part of the manual
has apparently been left out. With good reason I suppose:
IMO there simply is little use for JAVA_HOME unless someone is building Octave
from sources and wants Java support to be included. The Octave configure
script has some fairly capable stanzas for discovering the local Java
subsystem location ("JAVA_HOME") in build boxes. (AFAIK only on Mac OSX there
may be need/room for improvement. But AFAICS no Mac Octave dev has ever tried
to include Java support in recent builds - I may be wrong though.)

@Mike: if you still think a description of JAVA_HOME is required in the Octave
manual, it is better to enter a separate bug report for that. I won't have
time/priority anyway until somewhere around end of March.

Wrapping up: 
As: 
- the Java OF package isn't supported anymore,
- and for ordinary users JAVA_HOME isn't required,
- and Octave's build system generally doesn't need an explicit JAVA_HOME
setting,
I think I'll just close this bug with "Won't fix".


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38060>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/