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.
NetBeans 5.5 does not prevent projects from being cyclic dependent (A depends on B and B depends on A). Of course, this can only happen accidentally. Then, when you compile one of these projects, the Ant engine enters an infinite loop causing NetBeans to freeze. (init deps-jar init deps-jar ...)
Reassigning to "Ant" for evaluation
The GUI for various project types does attempt to prevent you from adding project dependencies in such a way as to create a loop. Did you manually edit configuration files so as to bypass this check? Detailed steps to reproduce the problem from scratch are required for evaluation. Also, what do you mean by "infinite loop" and "freeze"? Certainly if you submit an Ant script which loops, it will run forever and consume a lot of CPU. But you should be able to use Build | Stop Building to terminate it.
Created attachment 35917 [details] Contains two sample projects which can be used for reproducing the problem
Firstly, thanks for the quick response. Though I am not a native English speaker, I did my best in order to report this issue in an understandable way. The problem I encountered is definitely avoidable if you are careful. I didn't change the configuration manually, nor did I make any modifications to the settings which could seem to be related to this problem. Detailed description: Project 'one' (depends on 'two') one.MyComponentOne extends two.MyComponentTwo Project 'two' two.MyComponentTwo extends javax.swing.JComponent two.MyPanel extends javax.swing.JPanel Both projects have not been compiled yet, they are in a clean state. Now I am (accidentally, not intentionally) adding 'MyComponentOne' to 'MyPanel'. NetBeans correctly recognizes that project 'two' now depends on project 'one' and adds 'one' to the library of 'two'. This is the point when both projects are cyclic dependent. I think this mistake can be prevented by testing on cyclic dependencies. This time the IDE did not freeze. The sample projects are in the attachment. Keep on working on NetBeans, it is a great IDE!
You were using the form editor, rather than the project Properties dialog, to introduce the dependency. This is the critical information I was looking for.
I see that there has been a misunderstanding, but I am glad we resolved it.
Will try to implement a check when adding a project dependency.