Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using Lomboz plugin with Eclipse

email@hidden wrote:

>No, you probably just have to put
>/System/Library/Frameworks/JavaVM.framework/Classes/classes.jar on your
>classpath. Someone decided that it had to be done different.

But classes.jar is already on the boot-classpath, which is the property
named "sun.boot.class.path".

It's not in the CLASSPATH env-var, nor is it in "java.class.path", but that
hasn't been necessary or even recommended since the first appearance of JDK
1.2:
<http://java.sun.com/j2se/1.4/docs/guide/extensions/index.html>
<http://java.sun.com/j2se/1.3/docs/guide/extensions/index.html>

According to this reference:
<http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/classpath.html>

> If you are upgrading from an older version of the SDK software, your
> startup settings may include CLASSPATH settings that are no longer needed.
> You should remove any settings that are not application-specific, such as
> classes.zip. ...


>I have to warn you that this list has shown people prepared to defend that
>decision and to blame either you for not understanding or the Lombok
>people for doing something wrong that happens to work elsewhere.

"Happens to work elsewhere" != "Certain to work everywhere".

Speaking French happens to work in many countries (Algeria, Switzerland,
parts of Canada), but it won't get you very far in many other places (e.g.
Australia, Guatamala, South Africa). Nor will trying to spend Mexican
pesos in Texas. Such assumptions are naive, or at least uninformed.

The structure of a J2SE installation is not standardized.

There is a widespread assumption that the installed structure of Sun's Java
products is the installed structure of ALL Java products. This assumption
is utterly groundless, since a Java installation need not even use
jar-files for storing classes. As far as I can tell, even Sun doesn't
guarantee that the structure of its products won't change from release to
release, as it deems necessary.

In that sense, anyone who assumes a "jre/lib/tools.jar" is wrong. Or is at
least wrong for every Java product except Sun's current downloadable
products.

Nor am I defending Apple's decision. I'm simply pointing out that there is
permissible variation, and pretending there isn't is a portability error.

In some sense, Lomboz is in error. Either for assuming something is
portable when it isn't, or failing to document a non-portable aspect of
their product as such. Pick one and file a bug-report with the product's
maker.

Conceptually, it's similar to line-ending or file-separator variations.
There are countless faulty assumptions still made in those two simple
areas, despite easily accessible Internet RFCs that clearly say CR LF
terminates certain lines in a protocol, or the existence of File.separator
in Java.

-- GG
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Do not post admin requests to the list. They will be ignored.



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.