Bugzilla – Full Text Bug Listing
| Summary: | Missing nature results in an error log entry instead of a problem marker | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Konstantin Komissarchik <konstantin> |
| Component: | Resources | Assignee: | John Arthorne <john.arthorne> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Szymon.Brandys, thatnitind |
| Version: | 3.3 | ||
| Target Milestone: | 3.4 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=489540 | ||
| Whiteboard: | |||
I also opened a related bug to track similar behavior as it applies to builders: https://bugs.eclipse.org/bugs/show_bug.cgi?id=178131 Similar to bug 178131. In this case the message is logged when someone removes an nature whose extension no longer exists in the install. As you noted, this is a normal occurrence in the case of a migration where the nature has been intentionally removed. It is no longer being logged. Verified in I20071210-1800. |
If a project refers to a nature id which is not found in the Eclipse install that the user is running, the platform logs an info message in the PDE error log that looks like this: "Missing project nature extension for {x}." The problem that we are running into is that this behavior gets in a way of migration. BEA has been building on Eclipse for a while now and we have users whose projects need to migrated to BEA's new tooling. As part of the migration some natures are removed, others are renamed, etc. We run migration when we detect that a project has been imported. This works fine except for the fact that the user can later stumble on the above log entry (that no longer applies) and get confused. This case might be better handled by using a problem marker rather than writting to a log. This way when the problem is resolved (like it would after our migration had a chance to run), the problem marker would disappear and leave nothing for the user to get confused by. If this approach makes sense, I would be willing to work on and contribute a patch for this. Let me know.