csspin_java.mvn

The csspin_java.mvn plugin can be used to provision a desired Maven version into the defined mvn.install_dir and making it available for use within the context of csspin. It also provides the mvn-task to execute Maven commands.

How to setup the csspin_java.java plugin?

For using the csspin_java.java plugin, a project’s spinfile.yaml must at least contain the following configuration.

Minimal configuration of spinfile.yaml to leverage csspin_java.mvn

plugin_packages:
    - csspin-java
plugins:
    - csspin_java.mvn
java:
    version: "19"

The provisioning of the plugins, its dependencies, Java, and Maven can be done via the well-known spin provision-command.

How to use the csspin_java.mvn plugin?

After provision, the plugin can be used to execute Maven commands as follows:

Using the csspin_java.mvn plugin

spin mvn --help

How to use a local Maven installation?

If a local Maven installation is available, the mvn.install_dir can be configured to point to the installation directory. The plugin will then use the local installation instead of provisioning a new one.

An alternative solution is to use the mvn.use parameter to pass the Maven executable.

csspin_java.mvn schema reference

mvn: 'object'

Configuration regarding the mvn plugin for csspin

mvn.exe: 'path'

The mvn executable

mvn.version: 'str'

Java version

mvn.goals: 'list'

List of goals to be executed by the mvn plugin

mvn.opts: 'list'

Options passed to the mvn call

mvn.defines: 'object'

Key-value pairs for defining properties in the mvn call

mvn.pom_file: 'path'

Path to the pom.xml file

mvn.packages: 'list'

List of packages to be included in the build

mvn.mirrors: 'list'

List of mirrors to use when pulling packages

mvn.url: 'str'

URL pointing to the mvn binary

mvn.use: 'str'

Use a local Apache Maven installation

mvn.install_dir: 'path'

Directory to store caches

mvn.schema: 'object'

mvn.requires: 'object'

mvn.requires.spin: 'list'

mvn._requires: 'list'