a patch for the <compilerArgument> value not working propery. currently the entire value is used as a simple parameter, i think all that needs to happen is that the value needs to be splint on whitespace and each part added as a separate argument. this is what the patch does.
a more robust version may handle <cr> <lf> just in case.
if someone asks why not simply use <compilerArguments> tag, the reason is simple. currently the arguments tag works like this:
javac a b c
but it is not uncommon to have parameters with an equal sign, such as -Acom.mycom.myprocessor.param=value, there types of params cannot be modelled in compilerArguments currently because <a=b/> is not valid xml. maybe support should be added for this usecase if values start with a "=" so that
<Acom.mycom.myprocessor.param>=value</..> will be properly handled as a single param instead of being split into two.