NetBeans - Compile on Save and Track dependencies

[Wildam Martin]

Hi folks,

it is starting to become a headache for me. I have some projects that
automatically do a clean & build removing my existing javadoc and I
have projects that sometimes need to be built twice to build without
errors (usually problems with symbols not found).

I have quite modularized architecture with several different libraries
and plugin technologies. I usually specify the project folder in
Project Properties->Libraries which always shows that it uses the
compiled files from the dist folder.

I noticed that some older projects have different (default) settings
for "compile on save" and "track java dependencies". So at this point
I have a mixture. :-(

I searched the net and found a strange recommendation at:
http://wiki.netbeans.org/CompileOnSave#J2SE_Projects

> In particular, the following changes are proposed to the J2SE project properties:
> * remove "Track Java Dependencies" checkbox from the Build/Compiling tab
> * add "Enable Quick Run" checkbox to the Run tab

Why should I turn the tracking off for J2SE projects (I would rather
have expected to better turn it off for JEE projects...) and what the
hack is "Enable Quick Run" - I can't find that.

http://wiki.netbeans.org/FaqCompileOnSave
is even more irritating to me as I don't really understand now, how
the whole compile and build process works (I even don't use maven so
it should be easier). When I debug everything is compiled differently
then when building? - Then why does NetBeans prevent me often from
building saying that already compiled because compile-on-save is on.
Either documentation must be wrong (or just missleading - that is also
possible) or NetBeans has bugs or it is just my "misconfiguration".

Primary question: How should I have my project settings for "compile
on save" and "Track Java dependencies" - and should I rather create a
library in netbeans adding the jars in dist and link directly to that
instead of linking directly the project? (I am doing Java SE only).

--
Martin Wildam

http://www.google.com/profiles/mwildam

[Wildam Martin]

Oh, and on the libraries node in the project properties tree I have an
option "Build projects on classpath" - should that be enabled or not?

[hlovatt]

I have found both of these options buggy and regularly turn them off :
(

I have filed bug reports and noticed that others have also filed
against these.

If you have a repeatable problem se if there is a bug report, if not
file one.

-- Howard.

[Wildam Martin]

On Tue, Aug 24, 2010 at 08:10, hlovatt <howard...@gmail.com> wrote:
> I have found both of these options buggy and regularly turn them off :

Thank you for mentioning. I don't know why I - while starting to
become mad - always still think that it's my fault if something is not
working...

You mean "compile on save" and "track java dependencies"?

What is with "compile projects on classpath"?