staterefa.blogg.se

If you have imported it as a jar file - do you know what level of theĬompiler was used to build it before you imported it?

Understands 1.5.0 built code) but not vice versa. AspectJ is always compatible moving forwards (the 1.6.0 weaver For example, if I compiled it withġ.6.0 then wove it with the 1.5.0 weaver, I would see something like Usually it is because a newer version of aspectj was used to build theĬode than was used to weave it. Something and the aspectj level that is being used to weave it. Indicates a mismatch between the aspectj level that was used to build Now, because AOPHiddenMetrics probably already has someĪnnotations from ajc (from a newer version of ajc I must say), then when CaesarJ calls the weaver 1.2.1, it gets confused by those annotations. But when you use the call pointcut, you will match things inside many libraries that call java.*., including AOPHiddenMetrics. Since there is no annotations there, this is no problem. Second, when you use this execution pointcut you will only match methods inside the java runtime library (because of your regular _expression_). So it first generates bytecode and annotates it with some ajc specific stuff and then call the weaver on it.

Oggetto: Re: A weaving problem?įirst, the CaesarJ compiler uses the AspectJ Weaver version 1.2.1.