FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 1100 : 1.0.1 "expert" does not find Java
Last modified: 2010-06-06 07:32
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
CLOSED
Resolution:
WORKSFORME -
Pr
i
ority:
P5
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
MrFeinberg
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2008-12-12 10:51
When I double-click on the processing.exe application, version 1.0.1, it
looks for a jre in its own directory, then gives up. It does not examine
JAVA_HOME, nor search the PATH for a Java (I know this from watching it
with a couple of trace tools). The last version I downloaded, 0135-expert,
correctly finds an existing JRE and starts up.
Additional Comment
#1 From MrFeinberg 2008-12-12 10:52
I should say, this is a showstopper. :)
Additional Comment
#2 From fry 2008-12-12 10:55
Do you get any sort of error message?
Try starting from the command line with:
path\to\processing.exe --l4j-debug
Also make sure that you have a full JDK (not just a JRE), and that it's JDK
1.5 or later.
Additional Comment
#3 From MrFeinberg 2008-12-12 11:01
CmdLine: C:\Documents and
Settings\Administrator\Desktop\processing-1.0.1-expert\processing.exe
--l4j-debug
WOW64: no
Working dir: C:\Documents and
Settings\Administrator\Desktop\processing-1.0.1-expert\.
Bundled JRE: java
Check launcher: C:\Documents and
Settings\Administrator\Desktop\processing-1.0.1-expert\java\bin\javaw.exe (n/a)
64-bit search: SOFTWARE\JavaSoft\Java Development Kit...
32-bit search: SOFTWARE\JavaSoft\Java Development Kit...
64-bit search: SOFTWARE\IBM\Java Development Kit...
32-bit search: SOFTWARE\IBM\Java Development Kit...
Open URL:
http://java.sun.com/javase/downloads/
I do have a number of JDKs installed, and, as I said, the version
0135-expert works as expected. It seems to me like a bug in launch4j or a
misconfiguration in the launcher. It should inspect and respect JAVA_HOME,
which, on my box, points to a full SDK. It should also inspect and search
the PATH.
Additional Comment
#4 From fry 2009-02-20 11:51
Hm, will have to check into that. Wonder if the IBM JVMs are somehow
confusing launch4j.
Additional Comment
#5 From MrFeinberg 2009-02-20 12:05
I don't have any IBM JDKs installed. I suppose I might once have... But the
point is that it should look *first* for a JAVA_HOME environment variable
and respect that!
Additional Comment
#6 From fry 2009-02-20 12:16
Hrm, that's not what these lines are?
64-bit search: SOFTWARE\IBM\Java Development Kit...
32-bit search: SOFTWARE\IBM\Java Development Kit...
I've not seen those on other machines--maybe registry boogers?
I threw out my launcher from earlier releases hoping that launch4j would
fix things, but unfortunately it's two steps forward, one step back as
we've got another set of quirks to be tracked down. At least we're one step
forward. I think. Weee!
Additional Comment
#7 From fry 2010-06-05 09:50
is this still a problem?