Community
Participate
Working Groups
Circular dependency error msg should be a warning msg if preference is not checked 1) Go to the preference settings and locate the "java compiler" preferences. 2) There is a tab labeled "other" which has a checkbox "Stop building when an invalid classpath is detected." If this checkbox is not checked, projects will attempt to build/compile even with a circular dependency. However, the message "A cycle was detected in the projects classpath" is showing up in the task list as an error message (red X). We feel it should really be a warning message in this case. There is no way to remove this message from the task list (short of removing the circular dependency itself). We have circular dependencies that we can't get rid of. Having a error message (red X) show up that we can never remove is undesirable. One further comment about circular dependencies: We're looking at what we can do to resolve them but it is not something that can be resolved quickly. We have numerous (20+) EJB projects containing numerous (Can't remember how many) EJBs.
This would make sense. Need to see how we would re-compute these markers when the setting change, but this would definitely make sense.
Is there any new news on this problem and how soon it could be resolved?
*** This bug has been marked as a duplicate of 23318 ***