I am in the process of converting a ridiculously complicated ant build (well over 200 build files) to maven. One feature of the existing build is that it checks for use of unsupported JDKs by compiling with a specific boot class path. It is my understanding that the accepted Maven way to do that is via use of the animal sniffer maven plugin, but I note that using that plugin adds a noticeable amount of time to the build (for this step with over 5000 classes, it is taking close to a minute).
It leads to me to wonder if I shouldn't switch back to using the boot class path. What arguments are there, pro and con, for the plugin approach? Thanks, Russ ----------------- Come read my webnovel, Take a Lemon <http://www.takealemon.com>, and listen to the Misfile radio play <http://www.fuzzyfacetheater.com/misfile/>!
