Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U06A03HV1>: I’m getting some build failures for

                     E   	                   compile(examples/src/scala/org/pantsbuild/example/fact:fact-js) failed: Zinc compile failed.
                     E   	FAILURE: Compilation failure: Failed jobs: compile(examples/src/scala/org/pantsbuild/example/fact:fact-js)

can’t repro locally but I seem to be in sync with master as well.

compile(examples/src/scala/org/pantsbuild/example/fact:fact-js) failed: Zinc compile failed

<https://travis-ci.org/pantsbuild/pants/jobs/105298178>

tests pass here and locally though: <https://travis-ci.org/digwanderlust/pants/builds/105298161>

<@U0JSN507N>: You're registering a target as a task

You don't register tasks via BuildFileAliases

(yes, they're different things currently)

```task(name='depjson', action=DepJson).install()```

```from pants.goal.task_registrar import TaskRegistrar as task```

<@U0JSN507N>: A working example of both goals and aliases:

<https://github.com/foursquare/fsqio/blob/master/src/python/fsqio/pants/register.py>

<@U053HNE90>: I feel like I need more conceptual grounding here. I've tried to read the examples and don't understand what I'm reading.

In particular I read <https://pantsbuild.github.io/howto_plugin.html> which defines a HadoopBinary task

So are you familiar with the semantic meaning of targets vs tasks vs goals?

rereads <https://pantsbuild.github.io/internals.html>

Hilariously, internally we have both a target and a task named `HadoopBinary`

One is the target that represents a hadoop binary, and one is the task that takes hadoop binary targets and spits out specialized fat jars

OK, so, when I'm creating BUILD files and using `java_library`, I'm using the `java_library` _task_ to define a _target_ named foo, and I use the `compile` goal to invoke it, right? Did I say that correctly?