A `jar
` file with first and third-party code bundled for deploys.
The JAR will contain class files for both first-party code and third-party dependencies, all in a common directory structure.
Backend: <span style="color: purple"><code>pants.backend.experimental.java</code></span>
## <code>dependencies</code>
<span style="color: purple">type: <code>Iterable[str] | None</code></span> <span style="color: green">default: <code>None</code></span>
Addresses to other targets that this target depends on, e.g. ['helloworld/subdir:lib', 'helloworld/main.py:lib', '3rdparty:reqs#django'].
This augments any dependencies inferred by Pants, such as by analyzing your imports. Use `./pants dependencies
` or `./pants peek
` on this target to get the final result.
See [Targets and BUILD files](🔗)#target-addresses and [Targets and BUILD files](🔗)#target-generation for more about how addresses are formed, including for generated targets. You can also run `./pants list ::
` to find all addresses in your project, or `./pants list dir:
` to find all addresses defined in that directory.
If the target is in the same BUILD file, you can leave off the BUILD file path, e.g. `:tgt
` instead of `helloworld/subdir:tgt
`. For generated first-party addresses, use `./
` for the file path, e.g. `./main.py:tgt
`; for all other generated targets, use `:tgt#generated_name
`.
You may exclude dependencies by prefixing with `!
`, e.g. `['!helloworld/subdir:lib', '!./sibling.txt']
`. Ignores are intended for false positives with dependency inference; otherwise, simply leave off the dependency from the BUILD file.
## <code>description</code>
<span style="color: purple">type: <code>str | None</code></span> <span style="color: green">default: <code>None</code></span>
A human-readable description of the target.
Use `./pants list --documented ::
` to see all targets with descriptions.
## <code>main</code>
<span style="color: purple">type: <code>str</code></span> <span style="color: green">required</span>
`.
`-separated name of the JVM class containing the `main()
` method to be called when executing this JAR.
## <code>output_path</code>
<span style="color: purple">type: <code>str | None</code></span> <span style="color: green">default: <code>None</code></span>
Where the built asset should be located.
If undefined, this will use the path to the BUILD file, followed by the target name. For example, `src/python/project:app
` would be `src.python.project/app.ext
`.
When running `./pants package
`, this path will be prefixed by `--distdir
` (e.g. `dist/
`).
Warning: setting this value risks naming collisions with other package targets you may have.
## <code>resolve</code>
<span style="color: purple">type: <code>str | None</code></span> <span style="color: green">default: <code>None</code></span>
The resolve from `[jvm].resolves
` to use when compiling this target.
If not defined, will default to `[jvm].default_resolve
`.
## <code>restartable</code>
<span style="color: purple">type: <code>bool</code></span> <span style="color: green">default: <code>False</code></span>
If true, runs of this target with the `run
` goal may be interrupted and restarted when its input files change.
## <code>tags</code>
<span style="color: purple">type: <code>Iterable[str] | None</code></span> <span style="color: green">default: <code>None</code></span>
Arbitrary strings to describe a target.
For example, you may tag some test targets with 'integration_test' so that you could run `./pants --tag='integration_test' test ::
` to only run on targets with that tag.