I am working on issue 21676 and I have run the IDE with this patch
http://www.netbeans.org/issues/showattachment.cgi?attach_id=5081 and the
arguments described there. I have found out that following classes are being
loaded into the system on startup. Please investigate why they are loaded and
prevent that to happen. Thanks.
These classes are also loaded, but I do not know how to prevent that. But if you
do try to fix it too.
I don't understand why this is P2 issue. Lowering priority.
Because of the keyword PERF? Is not performance important to you? Are
not you interested in knowning why the hell JavaCompilerType is
initialized on startup?
I'll be really glad if you could find out why the class is loaded into
the VM. I am searching for list of ways how a class can be loaded
during startup and I need your help.
java.environment* classes are loaded on behalf of the AutoMounter
support in core when it recognizes module-provided JARs that are
registered in the layer.
The CompilerType is not loaded on the startup, but rather at the first
query for the compiler. Since Java nodes need to check up-to-date
state to properly badge their icon, it can happen quite early - when a
Java node appears on screen. If unhappy, please disable "Show Compile
Status" in Java sources.
Resolved for 3.4.x or earlier, no new info since then -> closing.