When SourceGenerator doesn't omit warnings, it hangs build waiting for confirmation

If you set SourceGenerator to NOT omit warnings (using the odd notion of setting "warnings" to "true"), and it's used in a normal build situation where the castor process is forked, the SourceGenerator will wait for input confirming whether to continue or not, even BEFORE printing the warning. In this situation, the build is hung, and will not complete. If the build is run from the command line on a console, and the user pressed ^C at this point, the forked process spins away, creating even more confusion.

In general, I'd say there's not much point in prompting for whether to continue or not. A warning is a warning. It should always continue on. If the generated code is broken, it won't compile. At least printing the warning gives me more information about what's wrong.

if there's a desire to not change existing behavior, then add another command-line option, like "-continue", to indicate to always continue on warnings. The doc for this should recommend using that flag in anything but a pure direct command-line execution of the SourceGenerator (just about the only situation where prompting can be of any use).

Just in case, I'll attach a zip file containing my Ant build file, properties file, and the xsd I'm trying to process.