It is suggested that the preferrred way of creating the
information for a Java package, such that the javadoc tool recognizes it as such, while creating
the javadoc documentation.
I decided to take this advice and immediately landed into problem of inconsistency with it. I could not
create this file as a Java source file, using the NetBeans IDE because it is not a proper java class name...
We have been requested to use static imports sparingly. I like that advice. Use your judgment to actually use this support.
But frankly, articles, presentations I have seen use the stdout, the "out" field of java.lang.System as imported statically. But, the following program does not compile:
class Format {
public static void main(final String[] args) {
out.format("Hello, World!");
}
}...
As Scott Oaks has pointed out, the Application Platform SDK (formerly known as Java EE SDK) has been released.
One of the things that quickly catches the eye is on-demand attach for JConsole that Java SE 6 has. The idea is that you can now avoid the non-intuitive Java System Properties (that were essential in Java SE 5) and still manage and monitor a Java SE 6 VM, on-demand.
So all you do is:...
