Deeper selection of internal targets during publishing
Review Request #1213 - Created Oct. 24, 2014 and submitted
|areitz, johanoskarsson, patricklaw, tejal|
The current behavior of selecting directly declared Jarable targets broke ages ago during Patrick's target refactor. In order to appropriately walk through intermediate jar_library/target declarations, we need to recurse.
It's common practice internally to have a top-level alias (a 'target' declaration) to point deeper into the directory structure to an actual java_library or scala_library. This meant that publishing was 1) ignoring those deps during fingerprint calculation and 2) not including them via DependencyWriter in written poms.
test publishes; will follow up to add unit tests here if things look sane.
Expanded the comment and added a test
Revision 2 (+68 -41)