Bug 176905 - Failure in chained field declare annotations
Summary: Failure in chained field declare annotations
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.6.2   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-10 16:31 EST by Ron Bodkin CLA
Modified: 2012-04-03 15:41 EDT (History)
2 users (show)

See Also:

Attachments
Failing test case (2.58 KB, patch)
2007-03-10 16:33 EST, Ron Bodkin CLA 		aclement: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Bodkin CLA 2007-03-10 16:31:08 EST 
The following test case breaks with ajc. Interestingly, in a corresponding project AJDT shows the correct two annotations on the field, but a runtime reflection test for the presence of the annotation fails. The annotation has runtime retention and a more direct declare annotation passes the test. See attached failing test case.
Comment 1 Ron Bodkin CLA 2007-03-10 16:33:38 EST 
Created attachment 60506 [details]
Failing test case
Comment 2 Andrew Clement CLA 2007-10-26 06:49:42 EDT 
work into testcase and investigate behaviour for 1.5.4
Comment 3 Andrew Clement CLA 2008-08-22 18:09:36 EDT 
test and fix committed. thanks for the testcase.

The problem was that Deprecated was 'special' in that it was in the java.lang package and some crappy code decided to shorten special type signatures by trimming off the java.lang, thinking we'd continue to realise it was special.  We didn't and when it could not be resolved due to not having a package prefix we failed to match Ljava/lang/Deprecated; against just Deprecated and didn't add the other annotation from the second declare @field.