On Mon, Apr 15, 2013 at 1:39 PM, Andy Clement wrote:
> I presume the 'type not exposed to weaver' messages were for your types
> and not for JRE types?
>
That's correct.
> If we could distill down a simple scenario that displayed this problem, I
> am happy to debug into it.
>
Thanks. I have bu
Hi Archie,
What you are trying to do sounds reasonable. The unusual thing I do notice
is that you have the inpath and destdir set the same for your final iajc
call. That could introduce weirdness. The only strict ordering policy for
processing files is that aspects are processed before classes.
I have a question about the proper usage of the ant task, as well as
a (possible) bug report. I'm using AspectJ 1.7.1.
In my project I have a bunch of normal Java code and one custom aspect.
I also have other pre-compiled aspects supplied in 3rd party JAR files
(e.g., Spring's @Transactional, et
