Eclipse allows its users to configure its compiler and choose what constitutes a warning. Under this issue, a wide range of warnings will be looked at. Work will divided by groups of warning types and by module or groups of packages under child issues.
CAUTION
These fixes make backports harder because they often affect many files at once in scattered locations.
It might be best to make the changes gradually on per-package or per-module basis.
- is blocked by
-
JDK-8297332 Remove easy warnings in javafx.base
- Resolved
-
JDK-8297412 Remove easy warnings in javafx.fxml, javafx.media, javafx.swing, javafx.swt and javafx.web
- Resolved
-
JDK-8297413 Remove easy warnings in javafx.graphics
- Resolved
-
JDK-8297414 Remove easy warnings in javafx.controls
- Resolved
-
JDK-8306490 Fix raw type warnings in graphics
- Open
- relates to
-
JDK-8298200 Clean up raw type warnings in javafx.beans.property.* and com.sun.javafx.property.*
- Resolved
-
JDK-8298528 Clean up raw type warnings in base in bindings and collections packages
- Resolved
-
JDK-8289845 ☂ Remove unused imports
- Resolved
-
JDK-8290244 ☂ Fix missing @Override warnings
- Resolved
-
JDK-8289379 ☂ Fix errors and warnings generated by Eclipse
- Resolved