Community
Participate
Working Groups
Build ID: I20070323-1616 Steps To Reproduce: When importing or migrating an old and large workspace, often there are missing builders or repetitive failures in various projects. Is it reasonable to assume that if the builder/validator is missing for one project, it'll remain 'missing' for subsequent projects as well? Same applies for migration failures. The current behaviour appears to check each project, search and run each builder, and log missing builders in the error log. For a large workspace, the following message appears multiple times and likely a) adversely affect performance, and b) clutters the log file. !ENTRY org.eclipse.core.resources 2 1 2007-05-15 11:05:09.881 !MESSAGE Skipping builder xxx.projectbuilder for project PROJECT_XXX_EJB. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. An argument could be made that the user needs to know the missing builder(s) for each project. Maybe this list could be cached, and presented as a single entry in the log. More information: I'll try to get some hard performance data to make a stronger case.
Performance is not an issue because it is only logged once per session. However, I am considering turning the warnings in the log off because this frequently happens under normal circumstances and it does create clutter in the log. Another suggestion has been to instead create a warning marker on the project, which would allow adding a quick fix to remove the builder from the build spec (bug 178131).
*** This bug has been marked as a duplicate of bug 178131 ***
