java-avro
Avro IDL compiler (https://avro.apache.org/).
Backend: pants.backend.experimental.codegen.avro.java
Config section: [java-avro]
Basic options
None
Advanced options
artifacts
--java-avro-artifacts="['<str>', '<str>', ...]"
PANTS_JAVA_AVRO_ARTIFACTS
[java-avro]
artifacts = [
'<str>',
'<str>',
...,
]
[ "org.apache.avro:avro-tools:{version}" ]
Artifact requirements for this tool using specified as either the address of a jvm_artifact
target or, alternatively, as a colon-separated Maven coordinates (e.g., group:name:version
). For Maven coordinates, the string {version}
version will be substituted with the value of the [java-avro].version
option.
jvm_options
--java-avro-jvm-options="['<str>', '<str>', ...]"
PANTS_JAVA_AVRO_JVM_OPTIONS
[java-avro]
jvm_options = [
'<str>',
'<str>',
...,
]
[]
List of JVM options to pass to java-avro
JVM processes.
Options set here will be added to those set in [jvm].global_options
. Please check the documentation for the jvm
subsystem to see what values are accepted here.
lockfile
--java-avro-lockfile=<str>
PANTS_JAVA_AVRO_LOCKFILE
[java-avro]
lockfile = <str>
<default>
Path to a lockfile used for installing the tool.
Set to the string <default>
to use a lockfile provided by Pants, so long as you have not changed the --version
option. See https://github.com/pantsbuild/pants/blob/release_2.24.0a0/src/python/pants/backend/codegen/avro/java/avro-tools.default.lockfile.txt for the default lockfile contents.
To use a custom lockfile, set this option to a file path relative to the build root, then run pants generate-lockfiles --resolve=java-avro
.
version
--java-avro-version=<str>
PANTS_JAVA_AVRO_VERSION
[java-avro]
version = <str>
1.11.0
Version string for the tool. This is available for substitution in the [java-avro].artifacts
option by including the string {version}
.
Deprecated options
None
Related subsystems
None