Roedy said:
But you did not check what I said or quote it. What I said was
neither erroneous nor FUD.
You are playing an Eric Berne style game.
I'm not playing a game, I'm trying to get you to fix bad information on
your website.
The text has been extensively quoted in this thread, but if you insist,
I will quote it again here:
According to Sun's JAWS FAQ, in JDK 1.5, Java Web Start still
does not support Class-Path. Up until JDK 1.5, java.exe too
ignored this entry.
- from
http://mindprod.com/jgloss/jar.html
The erroneous statement is the second sentence. (I include the first
only because the second is incomprehensible without it. I was able to
substantiate it at
http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/faq.html#209.
I think including this link in your page would be an improvement.)
Roedy, I seemed to have touched a nerve by accusing you of spreading
FUD, so I apologize. I am one of those sarcastic, caustic
northeasterners (in the US) and sometimes by voice does not carry well
in the usenet. I know that you are not intentionally trying to spread
incorrect information. My intention was not to antagonize you and start
a pointless flamewar. I will endeavor to be more diplomatic in the future.
These are the facts concerning the Class-Path entry in manifest files of
jars:
- When started via the -jar option, the JRE will use the contents of
the Class-Path entry as the classpath for the JVM. I have seen this
work for 1.2, 1.3 and 1.4. There is no reason to expect it does not
work for 1.1 also.
- When a jar is included in the classpath, its Class-Path entry is
included in the classpath for the JVM. (This allows you to ship a
library consisting of multiple jars and have your clients include only
the one jar in the classpath.) I have seen this work in 1.4 and 1.5.
- I am not aware of any bugs affecting this feature, although there may
be some. But there is certainly not one that prevents it from working
for all JVMs prior to 1.5.
- Bug 4356783
(
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4356783) in
particular, which you have cited in other posts to support the above
statement, is a) not a bug, b) recommends that the Class-Path manifest
entry be used when starting the JVM with the -jar option.
Ray
Ray