| Summary: | Compile warnings in official build | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dani Megert <daniel_megert> |
| Component: | UI | Assignee: | Dani Megert <daniel_megert> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | christian.georgi, daniel_megert |
| Version: | 3.8 | ||
| Target Milestone: | 3.8 M6 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Dani Megert
This is due to usages of the raw/ungenerified 3.6 APIs. How to deal with these warnings? Marking them as suppressed would resolve the compiler warnings in the 3.7 build, but will reveal others if running against a 3.6 target. Or should we disable them in the project's compiler settings? (In reply to comment #1) > This is due to usages of the raw/ungenerified 3.6 APIs. How to deal with these > warnings? Marking them as suppressed would resolve the compiler warnings in > the 3.7 build, but will reveal others if running against a 3.6 target. I've added the @SuppressWarnings annotations and disabled the warning for unused tokens. Fixed in master: b5757d9dc84e7388e1892d00e00d8ba22773a5bc Verified in N20120202-2000. |