|AJDT builder vs. ajc/ltw [message #66946]
||Thu, 24 August 2006 09:41
| Ralf Ebert
Registered: July 2009
I'm currently experimenting with AspectJ and AJDT. I set up some aspects
for my project and load them via AspectJ LTW, everything just works fine.
Now I wanted to use AJDT to get these aspects visualized while developing
application code. Unfortunately, I encountered some problems for which I
couldn't find any solution:
- I wonder if there is a possibility to get the exact same configuration
as the LTW would use (via META-INF/aop.xml) without defining AspectJ
Aspect Paths's in the project configuration? Somehow, seeing the aspects
as they would work as configured in my aop.xml (and embedded jars aop.xml
files) seems to be the whole point of the aspect visualization...
- When adding the jar with my aspects explicitly added to the AspectJ
Aspect Path after a full build everything works fine, aspects gets shown
as expected in the Cross References and the Eclipse Build classfiles got
the aspects woven. Unfortunately, if I change something in a class (and an
incremental build gets triggered), the aspects are not woven in.
Incremental building for AspectJ is activated, it even says that the
changed class is woven again. Only a full build fixes this again. Should
this be working as I expect / are there any known problems / something
that I probably have done wrong?
Thanks in advance,
Powered by FUDForum
. Page generated in 0.02405 seconds