Bugzilla – Full Text Bug Listing
| Summary: | Default severity for missing baseline should be 'Error' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dani Megert <daniel_megert> | ||||
| Component: | API Tools | Assignee: | Dani Megert <daniel_megert> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ankur_sharma, curtis.windatt.public, Curtis_Windatt, pwebster | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.7 M5 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 408699 | ||||||
| Attachments: |
|
||||||
|
Description
Dani Megert
Created attachment 184628 [details]
Fix
Fixed in HEAD. Curtis, thanks for committing my fix but I also have commit rights ;-) This results in a number of errors when the current I-build is used for development. Ironically, it also flags errors in bundles org.eclipse.pde.api.tools and org.eclipse.pde.api.tools.ui : Description Resource Path Location Type An API baseline has not been set for the current workspace. org.eclipse.pde.api.tools Unknown Default API Baseline Problem An API baseline has not been set for the current workspace. org.eclipse.pde.api.tools.ui Unknown Default API Baseline Problem Please reconsider this change. If you'd like to go with it, having in mind the effect, I'd hope to see: - the quickfix added for it, and - the change needs to be announced on the eclipse-dev mailing list. For clarity, here are the steps: - open a new workspace using current I-build - check out bundle "org.eclipse.pde.api.tools.ui" from CVS - check out bundle "org.eclipse.pde.api.tools" from CVS - note that there is a error reported for both bundles (In reply to comment #4) > Please reconsider this change. If you'd like to go with it, having in mind the > effect, I'd hope to see: > - the quickfix added for it, and > - the change needs to be announced on the eclipse-dev mailing list. 1) A bundle that is marked with the api tooling nature is expected to follow api restrictions. API Tools can enforce those restrictions, but cannot function correctly without a baseline. The error is to make it clear that your tooling is not set up correctly. 2) There is a quickfix on the error that opens the preference page. 3) Announcing the change is a reasonable request. There have been previous attempts to encourage developers to keep their baseline up to date, this is a much more visible step. The error should only be reported if you have a project in your workspace that has API Tools enabled. If that's not the case then we have a bug ==> please open a new bug for that. Otherwise the error is exactly what we expect because otherwise errors in the bundle with enabled API Tools will go unnoticed. You can always change the default if you want to ignore API Tools. Verified in I20110124-1800. |