Scenario:
buy-in for using AspectJ is incomplete at my company, it would be *nice* if I
could minimally modify build.xml and the src tree in order to add logging with
an aspect.
I can figure out much of how to get from here to there, its the "minimally"
part that is the problem. Should I be looking at just adding this logging
aspect to the runtime of the application using runtime weaving? Are there
examples of this?
The incremental compilation which involves interactively pressing enter, r, or
q seems unlikely to be met with acceptance. Everyone is used to just building
within eclipse then running.
It seems to me like as long as the jar containing the logging aspect is in the
classpath that compiling one class at a time should be acceptable, I can't see
why ajc (or iajc) would have to be invoked with every .java file in the
sourcepath.
How do folks normally apply a logging aspect to a new project, where the
changes are not going to be checked in so effort would be minimal?
owen
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
