Whether you get benefit from going 2.8->2.9->3.0 (over just going 2.8->3.0) is probably a factor
of how big and complicated the project being upgraded is - I'd guess Facia Tool is quite big, so
breaking the changes down into smaller chunks might be worth it in terms of avoiding risk.

Note also that Play 2.9 actually uses Play-Json *2.10*, which is a bit surprising!

See also guardian/maintaining-scala-projects#4

As #307 introduces a
new artifact, unfortunately artifact compatibility checking will crash
out (reporting that it can't find the previous version of the brand new
artifact to check compatibility against). So, we have to disable the
check for now, and then revert this change after the new artifact is
released.