<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">Jose, your pragmatic approach is *very* much appreciated.</div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><b class="">In a top level project</b>, having explicitly <b class="">chosen</b> to specify the `warning_as_errors` option, </div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">a failed build as a result of warnings is <b class="">sensible</b>.</div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><b class="">In a dependency</b>, enforcing a top level build failure due to it’s own <b class="">deprecated code,</b></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">is at best, <b class="">unhelpful</b>.</div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">While upgrading a project to compile/run on a modern Erlang - it is nearly impossible to avoid </div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">the case where one achieves a successful compilation, yet experience a slew of deprecation warnings.</div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">I fork all my dependencies in a non-backward-compatibile way to work around this limitation, </div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">but this approach is less than desirable from the perspective of cohesion/fragmentation/anything really.</div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;"><br class=""></div><div class="" style="font-family: Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;">Bryan</div><div class=""><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>