Hi,
> Eclipse was using the AspectJ compiler when building, so all weaving was
> coming from the compiler and not the load-time weaver. Turning off aspectJ
> Capability for the project fixed the failure-to-update problem for affected
> classes but now I've lost all code help which comes from aspec
FOLLOW-UP:
It is turning out that my problem is actually two problems:
1st:
Eclipse was using the AspectJ compiler when building, so all weaving was
coming from the compiler and not the load-time weaver. Turning off aspectJ
Capability for the project fixed the failure-to-update problem for affect
Classes which are updated in certain ways (code changed, recompiled in
Eclipse) which are then affected by an aspect file at load-time, do not
reflect those changes.
My project is in Eclipse, using a WeavingURLClassLoader at the very
beginning of execution for fleshed-out reasons out of scope of t
