Re: [aspectj-users] Aspectj warning question

[Andy Clement <andrew.clement@xxxxxxxxx>]

The message means that in order to ‘do its job’ AspectJ would like to modify the named type but you haven’t supplied it either in source form or on the inpath (if a binary input). If you have only supplied it on the class path AspectJ can see it but not modify it.

It is an xlint and like all xlints it can be turned off -Xlint:ignore or supply a properties file that configures that specific lint off.

Or from 1.7.4 onwards individual xlints can be turned off at the command line: https://eclipse.org/aspectj/doc/released/README-174.html

If weaving is working, that is great, without knowing more about the scenario I can’t say what is the impact of AspectJ not being able to modify the specified type. I’d hope it had good reason to want to modify it but perhaps it will only manifest in a particular advice execution scenario.

cheers,

Andy

On Apr 27, 2015, at 11:39 PM, 이현동 <zoo001199@xxxxxxxxx> wrote:

Hi

I have a  question about compile warning log.
When i compile aj files , i found under log

"This affected tupe is not exposed to the weaver: [type]xlint:typeNotExposedToWeaver"

I dont know what this log mean.
But Weaving was work....

If somebody know this log, response plz.
Also how can o remove this log??

Thanks

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users