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.
This is speculative feature. Is it possible to improve the validation system in such a way that root cause conditions could be identified and dependent errors associated with root cause problems. Example: missing or broken WSDL/XSD import will result in many many individual errors being reported. However, all of those errors would be dependent on the missing broken import. Question is can the validation system detect such cases? Can the UI provide some indicator of this dependency (or supress the derived problems so that user is not distracted by the derivative problems). Open issue - are there enough cases where this can be done to justify engineering a solution?
For instance, all entities which use the same namespace prefix would be affected when that namespace is broken/invalid.
Open issue - is this just a special case of the "Fix/Repair this" feature? See bug 87875
Another potentially big feature. Probably too big for Gavotte. Maybe for beyond. Denis are you interested? Let's discuss.
It is the part of the "Fix/Repair this", bug 87875. *** This issue has been marked as a duplicate of 87875 ***