>> >> 2) Core tasks should do more parameter checking. On the java task, I >set >> failonerror to true AND fork to false. This should probably >> produce an error >> / warning.
>Why? Just because the current code always returns an error code of 0, >does >not mean this is a valid combination of attributes. In fact, I have been >working on a patch to capture System.exit calls and return the status value >even for non forked code. This would make this combination valid. I'm not saying anything about what the called program does or does not do. I'm just saying that when fork is not "true" -- failonerror is currently ignored. Since it is ignored a warning should be produced (just like jvmargs). In general I think all ignored parameters should produce warning messages. Paul
