Description Davy Toch 2007-07-29 05:58:09 EDT

We're using the AspectJ 1.1 Compiler Adapter class:

  org.aspectj.tools.ant.taskdefs.Ajc11CompilerAdapter

from ANT to call AJC.

We noticed that the AJC command-argument parser doesn't always do a strict checking of the arguments (cf attachment ant-ajc.log), e.g.:
1. if the passed '-source/-target' contain completely invalid values, it will only log a warning which is only shown in verbose mode
2. if the passed '-aspectpath' contains an invalid/corrupt entry, it will only log a warning

The risk is somebody does the build but doesn't notice the warnings in the build log. As a consequence an invalid binary is built in the end.

So I think it would be recommended to :

1. check more strictly the arguments and fail if they are invalid 

or

2. have an option passed to AJC (as a JVM property?), allowing AJC to enable/disable strict argument checking (so fail if one of the arguments is invalid)