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.
For now I see a lot of exceptions are reported against Core, those should be reported against : uml, visualweb, wsdl, .... But I don't see these components in query page, so i assume if you don't find appropriate component in your DB (means there aren't all these components), you select Core as default, don't you ? Because all packs are build on the top of the IDE, it would be much better to all of these components to DB.
we are goint to use a jar file suggestion with pseudo components more info is writen in http://www.netbeans.org/issues/show_bug.cgi?id=96565 it should solve this problem as default "unknowm" is going to be used to say we have no suggestion *** This issue has been marked as a duplicate of 96565 ***
Jindra, do you think it will solve the problem with missing modules in query page ?
In query page there are just modules with existing error in our DB, I don't see the reason to fill it with no more used components in issuezilla or something like that. The number of components is going to rise while finding errors from new components. Why do you want to have a query for components if there is no issue assigned to them. I feel it as useless data. After fixing #96565 we will be able to set correct components by web site for unknown components and since that we can generate also new components from pacs in query page. *** This issue has been marked as a duplicate of 96565 ***
> Why do you want to have a query for components if there is no issue assigned to them. first 3 lines of this report said : ------------ For now I see a lot of exceptions are reported against Core, those should be reported against : uml, visualweb, wsdl, .... ------------ so that's the reason. If we want to people use this tool, we need a way to reassign issues to the right component, for now a lot off them simply don't exist in DB. So my previous question was: Do you plan to go through all already reported exceptions and assign each of them once again - just to use algorithm you described in issue 96565 ?
Yes we are going to recalculate all the components by new algorithm and we are going to keep information if the component was assigned by algorithm or by hand not to change user's decision. Web console is going to be done to add new components not just to reassign to existing components. We have no fixed table of existing components. As I said the number of components is going to rise with new suggestions and reassignements made by users. I'll close this issue after having regenerated components if you find it better.
Ok Jindra, thanks for explanation.
I've regenerated components and there as a possibility to change the component to all existing in issuezilla.
v/c