| Summary: | When Helios-based IDE is widely-used for development, revise .settings/org.eclipse.jdt.core.prefs | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mike Norman <michael.norman> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P4 | CC: | michael.f.obrien |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
The difference between 'unchecked' and 'rawtypes' requires one to change the @SuppressWarning annotation in source, which could be in alot of places. Instead, previous behaviour can be maintained with an added system property in the eclipse.ini: -DsuppressRawWhenUnchecked=true The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
In Helios, the JDT compiler new settings and different behaviour for old settings - e.g. @SuppressWarnings("unchecked") - since some projects have their prefs checked-in, there will be different warnings depending on whether or not the IDE is Galileo- or Helios-based We should review these settings once use of Helios-based IDE is wide-spread amongst the committers.