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.
If user make file sets LD_LIBRARY_PATH, and Smart Build Analyzer is on, build fails. Output window shows message "... libBuildTrace.so: open failed: No such file or directory" which is a underlined as hyperlink, if user clicks it a dialog with description of the problem appears. The main issue is that user won't guess that (s)he should click on the message that concerns a .so file. Besides, in my case the message was scrolled up from the visible part of output window. So this message should be made more visible. For example, a balloon should be shown in addition. Or if output window contained the description in the bottom lines ("BUILD FAILED because of..." or alike), this would solve the problem either.
It would be fine if the dialog that appears would propose not "Configure Smart Build Analyzer", but "Switch Off Smart Build Analyzer" and just switch it off instead of showing Option Dialog with correct tab (which still have 12 controls, so user has to find "Smart Build Analyzer" on this page and switch it off)
I filed the related enhancement issue 210188. I think, combining the two will give us ideal solution.
Integrated into 'main-golden', will be available in build *201212130001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/8316afaf7089 User: Alexander Simon <alexvsimon@netbeans.org> Log: fixing Bug #210182 User doesn't know what to do if Smart Build Analyzer spoils build - fix missing Mac platform
Do not sure that it is a bug.
I'm quite sure it is a bug. Let me put on my user's hat. I pressed "build". I see error message: "... libBuildTrace.so: open failed: No such file or directory" I'm sure that my project does not contain or refer to libBuildTrace.so. What should I do? No answer. That's my problem. I should see a clear explanation, what happened and what can I do to fix this. It is *absolutely* impossible for user to guess that it's "Smart Build Analyser" option somewhere in project properties that spoils the build.