This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Methods which signature is public static void main(String[] _) are almost certainly intended to be application entry points, so they don't generally need Javadoc. Probably the "Missing Javadoc" warning/hint should be disabled for such methods. Visible when you create a new main class.
I want to rewrite the missing javadoc hint to the new hints api from jlahoda so it will not be a warning but a hint visible just in case you place the caret in a method signature by default. He plans options ui to customize this. I will look at it as time permits. BTW an easy fix of this could be to add javadoc to the template. I am not sure that omitting documentation of entry point arguments is a good idea. Is not it api contract between cmd line and the app? ;-)
It is customizable now.
What is customizable? I don't see any option in a dev build relating to main methods.
You can customize in Tools/Options if use JD hints at all, what scope should be analyzed (public, private, ...) and how it should be presented (error, warning, caret on line, ...). The same is valid for the main method. There is no plan to list such detailed options.