Bug 65925 - type flagged by XLint:invalidAbsoluteTypeName if not accessible
Summary: type flagged by XLint:invalidAbsoluteTypeName if not accessible
Status: RESOLVED DUPLICATE of bug 67591
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.2.1   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-07 02:42 EDT by Wes Isberg CLA
Modified: 2004-10-21 04:32 EDT (History)
0 users

See Also:

Attachments
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 Wes Isberg CLA 2004-06-07 02:42:19 EDT 
Type names that are valid but inaccessable seem to trigger
XLint:invalidAbsoluteTypeName.

e.g., for class C { private static class Nested { .. }}, 

    execution(void C.Nested.method())

provokes XLint but otherwise works correctly.

Test case put in
tests/bugs/invalidAbsoluteTypeName/False_InvalidAbsoluteTypeName.java.
Comment 1 Adrian Colyer CLA 2004-08-09 15:26:10 EDT 
marked as target 1.2.1
Comment 2 Andrew Clement CLA 2004-08-10 12:34:00 EDT 
I fixed one very similar to this one - I'll take it.
Comment 3 Andrew Clement CLA 2004-08-11 04:19:06 EDT 
The other bug was sooo similar in fact that the fix covers this case :) 
Resolving as dup of the one I fixed it under, bug 67591 (see that bug for more
info).

*** This bug has been marked as a duplicate of 67591 ***
Comment 4 Adrian Colyer CLA 2004-10-21 04:32:27 EDT 
Fix released as part of AspectJ 1.2.1