[ JDK VERSION : 1.6.0_07 ]

The feature recently introduced to NetBeans allowing for managing
"shared libraries" in a project specific folder drastically eased the
way how to deal with dependencies in ant based projects. Next step
however seems more than just logical: 

Having two project A and B, B depending upon A, so far A can be added
to B via "Libraries" -> "Add project" which, in the end, will add A's
"dist/projectA.jar" to the classpath of B, rigorously ignoring any
libraries and/or dependencies eventually added to A in the first
place. This does result in a couple of drawbacks:

- It is counter-intuitive, as even though depending projects on the
classpath get built automatically (i.e. A will be built while
building B), building B still will fail as long as dependencies of A
aren't manually added to B as well.

- It creates an immense amount of additional work as soon as, in a
more complex environment, dependencies have to be maintained /
updated / replaced across several projects.

- It does (talking about Eclipse Project support) confuse Eclipse
users who completely rely upon their IDE exporting project code along
with project dependencies to dependent projects.

This does have quite a high priority in my opinion as it seriously
does affect usability of NetBeans along with ant projects. In our
special use case, we have opted to use maven2 initially because of
absence of this feature, which, in turns (despite the fact that m2
integration in NetBeans so far is pretty good) still we then and how
have to pay by not using some of the tooling NetBeans would provide
but which does not yet work with maven2.