Community
Participate
Working Groups
When using aspects to declare methods on supertypes, if you build the supertype and aspect classes into an aspect library and then attempt to weave a client using the binary library, ajc complains about member collisions and behaves as if there are no exception clauses on the target supertype method declarations. See test cases in modules/tests/bugs/interfaceLibrary. (This was discovered and largely isolated by someone on the user's list.)
P2 because it prevents the use of aspect libraries if the aspect declares methods with exception clauses.
Added cc contact. (webcbozic@adelphia.net)
This is now fixed in the tree for 1.1.1. There were two separate bugs here. The easy one was that the declared exceptions were being lost on introduced methods. This was a simple matter of passing this information through. The hard bug showed up only with public concrete methods, and was unrelated to the declared exceptions. This required a fairly serious change to get correct signatures on binary types with introduced methods.
updated target milestone field to 1.1.1
