JDK-8027262 : Determine location for type annotations earlier in compiler pipeline
  • Type: Sub-task
  • Component: tools
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Won't Fix
  • Submitted: 2013-10-24
  • Updated: 2014-08-26
  • Resolved: 2014-06-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Fixed
Related Reports
Blocks :  
JDK-8042060 - Type parameter annotations don't work with multiple type parameters
Blocks :  
JDK-8036142 - Remove redundant call to annotateTypeLater with null Symbol
Blocks :  
JDK-8038263 - Refactor annotation handling after actualEnterAnnotations
Blocks :  
JDK-8033004 - Make base TypeAnnotationPosition data immutable, create better methods for obtaining base TypeAnnotationPositions
Relates :  
JDK-8056021 - checkin for JDK-8027262 breaks Checker Framework
Description
Presently, the location and type path information for a type annotation is determined by resolveFrame, which is called late in the pipeline, after repeating annotations handling in particular.  This is a source of problems, not the least of which is that the position of some annotations is not updated until after repeating annotations has built containers.

An alternative is to build location information during attribution, attach it to the JCAnnotation tree node, and use the information when attaching annotations to their respective symbols.
Comments
Needs merged codepaths to continue
24-03-2014
8-defer-request: See parent task for justification.
29-10-2013