|Re: [aspectj-users] Met [org.aspectj.lang.NoAspectBoundException] while running a post-compile woven (bytecode woven) apache thrift library|
I wondered if you had an opinion on this. Iâve been working on this under https://bugs.eclipse.org/bugs/show_bug.cgi?id=535086 . I canât decide if you should have to specify privileged in order for pertypewithin to match against types not visible from the aspect. Currently I have it so that pertypewithin will no longer match private types or default vis types in another package unless you specify privileged. If you do specify privilege the visibility is raised for those types during weaving so they are accessible (the auto raising of visibility is not unusual, we do it for other reasons at times).