Thanks Matthew/Kevin, for the discussion. I have never seen it that way but I think in a sense you are right. I'll have to think about it some more...
On 2/27/07, Kevin F <[EMAIL PROTECTED]> wrote:
Does anyone else have experience trying to enforce these kinds of constraints? Am I just trying to push AJ beyond its intended design so I should add CheckStyle or some other piece of technology to my projects? I also see that the S.C.O.P.E. AJ implementation based on ajc is much smarter about making static choices. Is it possible to replace the standard AJ compiler included in AJDT with this one?
"Scope" would have be my number one recommendation, too. It's based on abc, not ajc. You should have no problem replacing ajc with abc/Scope in a batch build process since abc provides an appropriate ant task, even. However, there is currently no integration of abc with AJDT because AJDT relies heavily on ajc being based on the Eclipse compiler which abc is not. (In fact, Eclipse's support for analyses of such kind is pretty weak to non-existent, unfortunately.) Eric -- Eric Bodden Sable Research Group McGill University, Montréal, Canada _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
