Properly deprecate the Dependencies alias.
Review Request #3196 - Created Dec. 1, 2015 and submitted
I killed the Dependencies/DeprecatedDependencies dichotomy, since we now have a proper deprecation mechanism. I left the Dependencies name because that's the one that may still be used externally.
CI passes: https://travis-ci.org/pantsbuild/pants/builds/94305475
Thanks a lot Benjy.
I think we need to break this more thoroughly immediately... since all checks for
Dependenciesinstances have been removed, any code still using them will break in mysterious ways.
Middle ground might be to both mark deprecated (so that we remember to remove it), and just raise an error inside this constructor.
If this is going to continue to be
==to Target, it should probably have its own deprecation? Or should it just extend Dependencies and explode immediately as above.
Addresses code review comments. In particular - causes a hard failure on usage of dependencies() or python_test_suite() targets.