Experimental minifeature in Java property sheet

[resending, first try was rejected from list]

In a dev build, take a look at the property sheet for a Java source 
file. (C-S-7 to show the window, or Properties from the context menu to 
show a dialog). I added a new section "Classpaths" showing some 
information about the classpaths used for the source file (according to 
the project, or whatever defines these classpaths, such as a library). 
The information overlaps that displayed in the Libraries node under a 
j2seproject to some extent, but only partially:

- shows compile, run, and boot classpaths distinctly

- works for non-project classes, insofar as it can

- correctly displays different results for e.g. unit tests than for a 
class in main sources

In a nutshell, it is just a source of backup information about what the 
IDE is doing, so if you suddenly see code completion or background error 
parsing not working correctly on some source file, you can quickly 
double-check what the IDE is trying to parse it with. Might be valuable 
esp. for freeform projects with complex <classpath> definitions, to 
double-check or troubleshoot your setup.

It also shows sources in preference to binaries, which can help 
troubleshoot things if your libraries are not set up correctly or something.

Might slow down the global property sheet display slightly if you are 
rapidly switching files, though I could not observe any such problem in 
informal testing; anyway NB no longer displays the global property sheet 
by default.

Any opinions? Can easily be disabled completely or enabled only when 
some system property is set; I just wanted to throw it out there and let 
people try it rather than try to describe it in the abstract.

-J.

-- 
Jesse Glick <mailto:[email protected]> x22801
NetBeans, Open APIs  <http://www.netbeans.org/>