Bug 366341

Summary:	Incremental compiler fails to detect right scope for annotation related code changes
Product:	[Eclipse Project] JDT	Reporter:	Andrey Loskutov <loskutov>
Component:	Core	Assignee:	Stephan Herrmann <stephan.herrmann>
Status:	VERIFIED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	amj87.iitr, srikanth_sankaran
Version:	3.8
Target Milestone:	3.8 M5
Hardware:	PC
OS:	All
Whiteboard:

Description Andrey Loskutov

2011-12-11 17:45:12 EST

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

Comment 1 Srikanth Sankaran

2011-12-11 21:24:12 EST

(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 ***

Comment 2 Srikanth Sankaran

2012-01-23 01:57:30 EST

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.