They stricted up package usage at some point. I'm not recalling
exactly where, you used to be able to import unpackaged classes but
can't anymore.
I thought there were times this meant the class was almost
inaccessible. But testing at the moment seems to indicate that you
can still reference the class fine with ...
Thing.main(new String[0]);
new Thing().main(new String[0]);
things like this.
Huh, I remember I started packaging a lot of my own unpackaged
because of this. But maybe it doesn't matter that much and if you
find unpackaged works for you there is no reason, other than
following recommended but not enforced guidelines, to package.
I tended to use unpackaged for command line tools classes. One word
lower case names seemed more Unix like than packaged java names.
e.g.
javac
seems more normal as a command than
com.sun.tools.javac.Main
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
