wide-energy-11069
01/22/2016, 9:03 PMancient-stone-50795
01/22/2016, 9:04 PMjolly-chef-92794
01/22/2016, 9:04 PMancient-stone-50795
01/22/2016, 9:04 PMancient-stone-50795
01/22/2016, 9:05 PMwide-energy-11069
01/22/2016, 9:07 PMjolly-chef-92794
01/22/2016, 9:09 PMwide-energy-11069
01/22/2016, 9:09 PMfancy-queen-20734
01/22/2016, 10:03 PMjolly-chef-92794
01/22/2016, 10:04 PMfancy-queen-20734
01/22/2016, 10:05 PMfancy-queen-20734
01/22/2016, 10:06 PMjolly-chef-92794
01/22/2016, 10:08 PMwide-energy-11069
01/22/2016, 10:30 PMwide-energy-11069
01/22/2016, 10:30 PMancient-stone-50795
01/22/2016, 10:31 PMancient-stone-50795
01/22/2016, 10:31 PMjolly-chef-92794
01/22/2016, 10:44 PMjar_library
objects from managed_dependencies
, kind of how python_requirements
works?witty-crayon-22786
01/22/2016, 10:48 PMPythonRequirementLibrary
isn't a macro, iircwitty-crayon-22786
01/22/2016, 10:50 PMwitty-crayon-22786
01/22/2016, 10:51 PMsrc/python/pants/backend/python/pants_requirement.py
is a macro which generates the more verbose formjolly-chef-92794
01/22/2016, 10:52 PMjolly-chef-92794
01/22/2016, 10:53 PMmanaged_jar_dependencies()
target with artifacts populated from a BUILD file?witty-crayon-22786
01/22/2016, 10:53 PMwitty-crayon-22786
01/22/2016, 10:54 PMwitty-crayon-22786
01/22/2016, 10:54 PMwitty-crayon-22786
01/22/2016, 10:54 PMjolly-chef-92794
01/22/2016, 10:55 PMjolly-chef-92794
01/22/2016, 10:56 PM3rdparty/managed:….
if you had a managed_jar_dependencies
in 3rdparty/managed/BUILD
(though at that point maybe it’d make sense to put them in 3rdparty/BUILD.managed
or something)jolly-chef-92794
01/23/2016, 12:09 AM