Re the Enforcer plugin rule breaking builds that passed before: Yes, can see the problem there. There would be a couple of ways to address it:
- Add a property on the rule (equivalent to Surefire's -DskipTests) which skips the deprecation errors, effectively restoring default warning behavior and negating the existence of the rule. - Add a flag on `mvn` itself (equivalent to -C / --strict-checksums, which turns checksum warnings into errors), which would turn dependency deprecation warnings into errors. This would remove the need for an enforcer rule. But it would add another flag to `mvn`, which already has many. Maybe there is an appropriate flag already that we could piggyback on? Chris --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
