[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check |
Date: |
Thu, 29 Mar 2018 17:16:57 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Follow-up Comment #6, bug #53510 (project octave):
@Mike(comment #4):
You mean a minimum required Java version for the io package?
In the io package there's only a check on availability of a Java JRE. Version
is retrieved but not invoked anywhere.
In the io package several Java dependent "interfaces" (~dependencies) have
been implemented. I'd need to check each of them to find out a minimum Java
version. But then again, each of those 'interfaces' comes in several versions
each with a separate minimum Java version.
So in the end I think I just don't bother.
In my own experience I found that those "interfaces" are fairly robust as
regards Java version; if problems arise I expect it to be due to too new a
Java version rather than too old.
Most people I get reports from have a fairly recent or the newest io package
version; few of them seem to have bothered to install Java and one of the
Java-based interfaces at all and rely on the native Octave (OCT) interface.
All of this probably doesn't answer your question directly, but I think / hope
it'll be clear enough for you to make a decision.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53510>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #53510] [octave-forge] (io) wrong java check, Muhali, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave-forge] (io) wrong java check, Dmitri A. Sergatskov, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, John W. Eaton, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Muhali, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Mike Miller, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Mike Miller, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Mike Miller, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Philip Nienhuis, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Philip Nienhuis, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Philip Nienhuis, 2018/03/29
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Philip Nienhuis, 2018/03/30
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Mike Miller, 2018/03/30
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Philip Nienhuis, 2018/03/30
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Markus Mützel, 2018/03/31
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Mike Miller, 2018/03/31
- [Octave-bug-tracker] [bug #53510] [octave forge] (io) wrong java check, Markus Mützel, 2018/03/31