I am finally getting a chance to test a recent 6.7 build.  I've created a simple suite with a few simple modules.

What I expected: 
One of these modules does not use the Utilities API, but I wanted to use a public class (Lookup) from Utilities API in
my unit test.  I right-clicked Unit Test Library, chose "Add Unit Test Dependency," selected Utilities API and clicked
OK.  I expected this would allow me to use that class in my unit test.

What I found:
I tried to call Lookup.getDefault(), but this reference gave "red squigglies" in the source editor for my unit test. 
The Quick Fix suggestion was to create a class called Lookup, rather then to import the one from the Utilities API. 
Sometimes it takes the editor a second or two to catch up, os I waited and tried again, but it still did not give me the
option of importing this class. I rebuilt the module and then the entire suite, but this did not fix it either, nor
could I manually type the class name in as an import statemen (doing so showed "red squigglies" on the import statement
as if this API's JAR file was not in the compile-time classpath). 

Eventually I tried adding a regular dependency on the Utilities API from my module (i.e. not a unit test dependency as
before).  This allowed me to import the Lookup class in my unit test.  I removed the regular dependency from my module,
but left the unit test dependency.  This still allowed me to use the class.

I was later able to reproduce this by adding a unit test dependency on the Window System API and attempting to use the
TopComponent class in my unit test, when the module containing the test did not have a regular dependency on the Window
System API.


Here are the relevant details of the configuration under which I experienced this:

Product Version: NetBeans IDE Dev (Build 200905120201)
Java: 1.6.0_12; Java HotSpot(TM) Client VM 11.2-b01
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)