Community
Participate
Working Groups
Build Identifier: 3.8 M4 AS IS: Looks like incremental compiler fails to detect right classes to recompile after changes related to the nullness contract errors/warnings. So if there are new parameter annotations added to the super class method return value or arguments, only the clean build detects the errors in subtypes implementing this method. TO BE: Incremental compiler should be able to catch right classes to check after changing the nullness contract of the method return value or arguments. Reproducible: Always
(In reply to comment #0) > So if there are new parameter annotations added to the super class method > return value or arguments, only the clean build detects the errors in subtypes > implementing this method. I think adding annotations to return value should already work. Anyways this will get checked as part of bug 365992 *** This bug has been marked as a duplicate of bug 365992 ***
Verified for 3.8 M5 using build id: I20120122-2000. Andrey my testing shows that changing the nullness status on return type does trigger an incremental build. If you find it to be otherwise, please open a fresh defect with a suitable test case. Thanks.