Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[aspectj-users] age-old incremental compile question

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


Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.

Back to the top