-warnings=false can hide actual 'Error' level issues

[greg-dove]

-warnings=false can hide actual 'Error' level issues unless you set 'create-target-with-errors=true'

switching off warnings can be helpful when working through priority issues while porting a large Flex codebase. (e.g. to remove 'bindable' or other warnings etc, which would have been present in the orignal Flex compilation and just focus on porting issues)

But getting to zero Errors (if warnings are false) can still still result in no build because some 'Warnings' are considered 'Errors'.

@todo Discuss on list, if this agreed to be wrong, then it should be fixed.

(I have not tried to check anything similar to this in Flex yet)

[joshtynjala]

If a build is failing because a warning, that seems like a bug to me. Whichever warnings are doing this should be errors instead, and they should not be hidden when -warnings=false.