Hi,
I'm using a current Eclipse version, so I've picked-up
AspectJ/ajc1.6.11 in my development environment. In my runtime
environment I'm stuck with 1.6.8 for now, so as expected on deployment
I'm seeing a v6 versus v7 version clash, per [1]. Unfortunate,
runtime is only one revision too old for
Hi Andy,
An additional clarification:
I'm noticing that this re-compilation of dependent classes behavior
seems to happen only for classes with methods that are advised by some
aspects. I'm not sure why it still happened when I commented out all
the aspects and did an Eclipse clean.
Thanks,
Jona
Hi Andy,
Thanks for the prompt response!
> Ideally sharing the source with me will be the fastest way to get it
> resolved, but if that isn't possible perhaps we can narrow down the
> problem:
> - if you comment out the aspects (or pieces of them) does it still happen?
> - anything unique about t
I am out of the office until 03/05/2011.
I am on vacation returning on Tuesday 3rd May 2011. I will respond to
your message as soon as I can.
Thank you.
Regards,
Neil Wall
Note: This is an automated response to your message "aspectj-users Digest,
Vol 74, Issue 11" sent on 28/4/11 17:00:24
Hi Jonathan,
> Why is that? Why does it need to recompile all dependent source files
> when all I've changed is a whitespace or comment? Please note that I
> am not changing the aspects or pointcuts here at all. What am I
> missing? Has anyone else encountered this?
If more than just the file you
Hi there,
I'm currently using Eclipse 3.6.2 with AJDT 2.1.2 (which comes with
AspectJ 1.6.11), with incremental compilation turned on. There are a
couple of aspects advising the java sources as well as some third
party aspects (primarily those from Spring).
I'm noticing in AJDT event trace view t
