bugGNU Octave - Bugs: bug #38060, Java package offers wrong advice...

 
 

bug #38060: Java package offers wrong advice for setting JAVA_HOME

Submitter:  None
Submitted:  Fri 11 Jan 2013 06:39:17 AM UTC
   
 
Category:  Octave Package Severity:  1 - Wish
Priority:  3 - Low Item Group:  Feature Request
Status:  Wont Fix Assigned to:  None
Originator Name:  Heimo Herttua Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 3.6.2
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 02 Mar 2014 03:06:21 PM UTC, 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".

Philip Nienhuis <philipnienhuis>
Group Member
Sat 22 Feb 2014 10:56:11 PM UTC, comment #3: 

Should this bug be reassigned to Octave itself? I don't see any documentation about JAVA_HOME in the Octave manual, can someone write up what is needed if anything, or point to excerpts from the java package that should be incorporated into the Octave manual if needed?

Mike Miller <mtmiller>
Group Member
Fri 11 Jan 2013 03:23:45 PM UTC, comment #2: 

This has been answered in the Help ML.

The OP simply hasn't read all the instructions in the wiki, esp. about the situation on Windows. I don't think he's much to blame for that as this info is hard to get anyway.

IMO the OP is right in that the pkg.m messages about misinstalled Java packages ARE misleading.

Philip Nienhuis <philipnienhuis>
Group Member
Fri 11 Jan 2013 02:22:53 PM UTC, comment #1: 

The functionality you seek just isn't implemented yet. This isn't a bug. It's a feature request.

The Java package has been integrated into core Octave in the development release, so your desired features may be implemented there later.

The only bug here is that setting JAVA_HOME is not well described.

Jordi GutiƩrrez Hermoso <jordigh>
Group Member
Fri 11 Jan 2013 06:39:17 AM UTC, original submission:  

I have Windows XP sp3 32 bit and Octave 3.6.2 gcc4.6.2.

Java package installation gives misleading information and does not seem to function, as described below.

I downloaded package java-1.2.9.tar.gz, and tried to install it with command:
pkg install java-1.2.9.tar.gz

I got an error message:
Error while trying to install Java package:
environment variable 'JAVA_HOME' has not been set.

The error message suggested to set JAVA_HOME as:
 (on Windows:)
   <JAVA_HOME>/jre/lib/<arch>/ contains a file jvm.cfg
 (<arch> depends on your system hardware, can be i386, x86_64, alpha, arm, ...)

So I tried to set it by command:
setenv("JAVA_HOME", "C:/Program Files/Java/jdk1.6.0_03/jre/lib/i386")

This did not help. Then on the web (http://wiki.octave.org/Java_package) I found different suggestion to set JAVA_HOME. So I tried following:
setenv("JAVA_HOME", "C:/Program Files/Java/jdk1.6.0_03")

After that the installation did not cause any errors. So the installation procedure gives misleading information on how to set JAVA_HOME.


Other thing, after seemingly successful installation java does not seem to work. I tried command:
octave:9>  s = javaObject ("java.lang.String", "Hello OctaveString")
and get warning:
the `javaObject' function is not yet implemented in Octave

Same happens with command:
v = javaObject ("java.util.Vector")

So it seems that java package installation did not work at all.

I am very confused.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by philipnienhuis (Posted a comment)
  • -email is unavailable- added by jordigh (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-03-02 philipnienhuis StatusPostponed Wont Fix
        Open/ClosedOpen Closed
    2013-01-11 jordigh Severity3 - Normal 1 - Wish
        Priority5 - Normal 3 - Low
        Item GroupInstallation Failure Feature Request
        StatusNone Postponed
        SummaryJava package installation misinformation and functionality. Java package offers wrong advice for setting JAVA_HOME

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code