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.
As the APIs don't prohibit circular dependencies (they hardly could), the projects build system should check for the errornous condition an report an informative error instead of entering an infinite loop.
This should already be handled in the build system during the build process as well as when using the user interface to set dependencies. If there is a specific test case please list the steps to reproduce.
1. create a Jar build target 2. open its customizer, on the third pane (content specification), check the checkbox next to itself, close the dialog 3. build the jar -- the compilation never finishes Btw, I thought there was no user interface to set dependencies anymore.
If you use the context menu from the output node you will see the build target dependencies action. This is one place where cycles are checked (although this menu does not allow self references). You can see this in your example by adding a dependency from jar to compiled classes and vice versa (the cycle should be reported). I hope this functionality will continue to exist as there is no other way to generically create dependencies, which is necessary to link arbitrary targets.
Thanks, I missed that (I was looking for it on the output target node I wanted to set dependencies for) Could this check be published in the APIs (if it is not yet) so that I can call it from the my jar content editor? That would be great! (see #35994)
So, does this still mean that buildsystem doesn't detect cyclic deps during the build? Or is this issue just duplicate of issue #35994?
I thought it was not implemented at all. But it looks like, it was implemented but there's a bug in it (try the steps-to-reproduce above). So it's still a valid defect.
Fixed and updated test cases
Works, no cycle.
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as CLOSED.