本文整理汇总了Python中pants.backend.jvm.subsystems.java.Java.global_plugin_dependency_specs方法的典型用法代码示例。如果您正苦于以下问题：Python Java.global_plugin_dependency_specs方法的具体用法？Python Java.global_plugin_dependency_specs怎么用？Python Java.global_plugin_dependency_specs使用的例子？那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类pants.backend.jvm.subsystems.java.Java的用法示例。
在下文中一共展示了Java.global_plugin_dependency_specs方法的1个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的Python代码示例。
示例1: traversable_dependency_specs
# 需要导入模块: from pants.backend.jvm.subsystems.java import Java [as 别名]
# 或者: from pants.backend.jvm.subsystems.java.Java import global_plugin_dependency_specs [as 别名]
def traversable_dependency_specs(self):
for spec in super(JvmTarget, self).traversable_dependency_specs:
yield spec
for resource_spec in self._resource_specs:
yield resource_spec
# Add deps on anything we might need to find plugins.
# Note that this will also add deps from scala targets to javac plugins, but there's
# no real harm in that, and the alternative is to check for .java sources, which would
# eagerly evaluate all the globs, which would be a performance drag for goals that
# otherwise wouldn't do that (like `list`).
for spec in Java.global_plugin_dependency_specs():
# Ensure that if this target is the plugin, we don't create a dep on ourself.
# Note that we can't do build graph dep checking here, so we will create a dep on our own
# deps, thus creating a cycle. Therefore an in-repo plugin that has JvmTarget deps
# can only be applied globally via the Java subsystem if you publish it first and then
# reference it as a JarLibrary (it can still be applied directly from the repo on targets
# that explicitly depend on it though). This is an unfortunate gotcha that will be addressed
# in the new engine.
if spec != self.address.spec:
yield spec