ensure build failure when vulnerable commons-collections are in use
ensure build failure when vulnerable commons-collections are in use

(they cause the vulnerability by just being on the classpath, cf.
https://opensource.googleblog.com/2017/03/operation-rosehub.html
and [COLLECTIONS-580] “If you have an endpoint that accepts
serialized Java objects (JMX, RMI, remote EJB, ...) you can […]
to create arbitrary remote code execution vulnerability.” and
CVE-2015-4852 and this is likely needed in EVERY parent POM,
even when it’s not directly used, as it can be pulled in as
transitive dependency)

fossamagna/liquibase,mattbertolini/liquibase,mattbertolini/liquibase,mbreslow/liquibase,dbmanul/dbmanul,liquibase/liquibase,fossamagna/liquibase,jimmycd/liquibase,mattbertolini/liquibase,mattbertolini/liquibase,liquibase/liquibase,mbreslow/liquibase,jimmycd/liquibase,NSIT/liquibase,dbmanul/dbmanul,dbmanul/dbmanul,NSIT/liquibase,NSIT/liquibase,dbmanul/dbmanul,liquibase/liquibase,NSIT/liquibase,mbreslow/liquibase,jimmycd/liquibase,mbreslow/liquibase,jimmycd/liquibase,fossamagna/liquibase