Bugzilla – Full Text Bug Listing
| Summary: | type flagged by XLint:invalidAbsoluteTypeName if not accessible | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Wes Isberg <wes> |
| Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1.2 | ||
| Target Milestone: | 1.2.1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
marked as target 1.2.1 I fixed one very similar to this one - I'll take it. 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 *** Fix released as part of AspectJ 1.2.1 |
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.