Reference

Table of contents

mod

Automated code remediation.

Usage

mod [parameters] [subcommands]

Options

NameDescription

--version

Display version info.

Subcommands

  • build: Generates LST artifacts for one or more repositories.

  • clean: Clean build and run artifacts produced by the CLI.

  • config: Global configuration options that are required by some CLI commands.

  • exec: Execute an arbitrary shell command recursively on selected repository roots.

  • git: Multi-repository git operations.

  • log: Manages a log aggregate.

  • list: Lists the repositories that can be built and published.

  • monitor: (INCUBATING) Launches an HTTP server used to monitor the CLI.

  • publish: Publishes the LST artifacts for one or more projects.

  • run: Runs an OpenRewrite recipe locally on pre-built LSTS.

  • run-history: Get information about the most recent recipe runs.

  • study: Produces studies from OpenRewrite recipe data tables locally.

  • generate-completion

mod build

Generates LST artifacts for one or more repositories.

Once generated, the artifacts can be uploaded to your artifact management tool so that Moderne can ingest them or they can be used to run recipes locally.

While it is possible to manually build and publish your artifacts, we strongly recommend setting up a Jenkins pipeline or GitHub actions for ingesting LST artifacts in bulk.

If the path itself is not a Git repository, then this command will recursively look through the directories to find Git repositories that match the repository-* options.

If this command executes successfully, the LST artifact for each project will be stored in a .moderne/build directory inside of each repository that is built.

If you've set up a connection with Moderne (by running the mod config moderne command), this command will attempt to download LST artifacts from Moderne instead of building them locally. This will allow you to quickly run recipes and make changes. If you do not want this command to look for LST artifacts in Moderne, you can add the --no-download flag.

Usage

mod build [parameters]

Examples

mod build /path/to/project

Parameters

NameDescription

path

The absolute or relative path on disk to a directory containing one or more checked-out Git repositories that you want to operate on. This typically takes the form of targeting a single, checked-out copy of a Git repository or it can be a folder containing a collection of Git repositories that will be discovered by recursively scanning the initial provided directory.

Options

NameDescriptionExample

--dry-run

Do not actually build the LST(s), but list the steps that would be required to do so.

--no-download

Do not attempt to download LSTs from Moderne.

--offline

When an underlying build tool has an offline mode, enable it.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

mod clean

Clean build and run artifacts produced by the CLI.

Can be filtered to only clean certain artifacts.

Usage

mod clean [parameters] [subcommands]

Examples

mod clean builds /path/to/project --keep 1

Subcommands

  • builds: Clean build artifacts produced by the CLI.

  • runs: Clean run artifacts produced by the CLI.

mod clean builds

Clean build artifacts produced by the CLI.

Can be filtered to only clean certain artifacts.

Usage

mod clean builds [parameters]

Examples

mod clean builds /path/to/project --keep 1

Parameters

NameDescription

path

The absolute or relative path on disk to a directory containing one or more checked-out Git repositories that you want to operate on. This typically takes the form of targeting a single, checked-out copy of a Git repository or it can be a folder containing a collection of Git repositories that will be discovered by recursively scanning the initial provided directory.

Options

NameDescriptionExample

--keep

Keep this many run artifacts and clean all others.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

mod clean runs

Clean run artifacts produced by the CLI.

Can be filtered to only clean certain artifacts.

Usage

mod clean runs [parameters]

Examples

mod clean runs /path/to/project --keep 1

Parameters

NameDescription

path

The absolute or relative path on disk to a directory containing one or more checked-out Git repositories that you want to operate on. This typically takes the form of targeting a single, checked-out copy of a Git repository or it can be a folder containing a collection of Git repositories that will be discovered by recursively scanning the initial provided directory.

Options

NameDescriptionExample

--keep

Keep this many run artifacts and clean all others.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

mod config

Global configuration options that are required by some CLI commands.

Configuration set here is used as needed in all subsequent commands.

Usage

mod config [parameters] [subcommands]

Examples

mod config moderne edit --api <tenant-api-gateway> --token <token>

Subcommands

  • build: Configures build tools used to produce LSTs.

  • environment: The build environment that the CLI is running in.

  • features: Configures experimental features.

  • http: Configures HTTP options that will be used throughout the CLI.

  • java: Configures Java options used for building LSTs and running recipes.

  • license: Configure a license key.

  • lsts: Configures LSTs production and publishing.

  • moderne: Configures the connection to Moderne. Must be configured before you can install and run recipes.

  • recipes: Configures the recipe marketplace available to the CLI. Must be configured before you can run recipes.

  • scm: Configures source code management.

  • user: Configure the active user.

mod config build

Configures build tools used to produce LSTs.

Usage

mod config build [parameters] [subcommands]

Subcommands

  • active-styles: Configure the active styles to use when building LSTs.

  • bazel: Configures the Bazel build tool.

  • gradle: Configures Gradle as it is used to resolve recipe dependencies and when running recipes.

  • maven: Configures Maven as it is used for LST production, resolving recipe dependencies, and when running recipes.

mod config build active-styles

Configure the active styles to use when building LSTs.

Overriding active styles circumvents auto-detection of styles in the production of LSTs.

Usage

mod config build active-styles [parameters] [subcommands]

Subcommands

  • delete: Removes overriding active styles.

  • edit: Configure the active styles to use when building LSTs.

  • show: Displays the configured overriding active styles.

mod config build active-styles delete

Removes overriding active styles.

Usage

mod config build active-styles delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build active-styles edit

Configure the active styles to use when building LSTs.

Overriding active styles circumvents auto-detection of styles in the production of LSTs.

Usage

mod config build active-styles edit [parameters]

Parameters

NameDescription

activeStyles

Additional build arguments that are added to the end of the Gradle command line.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build active-styles show

Displays the configured overriding active styles.

Usage

mod config build active-styles show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build bazel

Configures the Bazel build tool.

Usage

mod config build bazel [parameters] [subcommands]

Examples

mod config build bazel rule edit "//:java-maven-lib"

Subcommands

  • rule: Configure the Bazel rule used to build LSTs.

mod config build bazel rule

Configure the Bazel rule used to build LSTs.

The rule affects how the project is built.

Usage

mod config build bazel rule [parameters] [subcommands]

Subcommands

  • delete: Removes Bazel build rule customization.

  • edit: Configure Bazel build rule.

  • show: Displays the configured Bazel build rule.

mod config build bazel rule delete

Removes Bazel build rule customization.

Usage

mod config build bazel rule delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build bazel rule edit

Configure Bazel build rule.

Usage

mod config build bazel rule edit [parameters]

Parameters

NameDescription

rule

The Bazel build rule to use when building LSTs.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build bazel rule show

Displays the configured Bazel build rule.

Usage

mod config build bazel rule show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle

Configures Gradle as it is used to resolve recipe dependencies and when running recipes.

Usage

mod config build gradle [parameters] [subcommands]

Examples

mod config build gradle arguments edit --refresh-dependencies

Subcommands

  • arguments: Configure Gradle build arguments.

  • root: (INCUBATING) Configure the directory containing the Gradle root build. This could be . to force the CLI to use the root directory of the repository as the Gradle build and look no deeper.

mod config build gradle arguments

Configure Gradle build arguments.

Build arguments are added to the end of the Gradle command line when building LSTs.

Usage

mod config build gradle arguments [parameters] [subcommands]

Subcommands

  • delete: Removes additional build arguments for Gradle.

  • edit: Configure Gradle build arguments.

  • show: Displays the configured Gradle additional build arguments.

mod config build gradle arguments delete

Removes additional build arguments for Gradle.

Usage

mod config build gradle arguments delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle arguments edit

Configure Gradle build arguments.

Build arguments are added to the end of the Gradle command line when building LSTs.

Usage

mod config build gradle arguments edit [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle arguments show

Displays the configured Gradle additional build arguments.

Usage

mod config build gradle arguments show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle root

(INCUBATING) Configure the directory containing the Gradle root build. This could be . to force the CLI to use the root directory of the repository as the Gradle build and look no deeper.

When this is set, the CLI does not attempt to find root Gradle builds in subdirectories or siblings recursively.

Usage

mod config build gradle root [parameters] [subcommands]

Subcommands

  • delete: Removes the configured directory containing the Gradle root build.

  • edit: Configure the directory containing the Gradle root build.

  • show: Displays the configured directory containing the Gradle root build.

mod config build gradle root delete

Removes the configured directory containing the Gradle root build.

Usage

mod config build gradle root delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle root edit

Configure the directory containing the Gradle root build.

When this is set, the CLI does not attempt to find root Gradle builds in subdirectories or siblings recursively.

Usage

mod config build gradle root edit [parameters]

Parameters

NameDescription

root

The directory containing the Gradle root build.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build gradle root show

Displays the configured directory containing the Gradle root build.

Usage

mod config build gradle root show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven

Configures Maven as it is used for LST production, resolving recipe dependencies, and when running recipes.

Usage

mod config build maven [parameters] [subcommands]

Examples

mod config build maven settings edit <path-to-settings.xml>

Subcommands

  • arguments: Configure Maven build arguments.

  • settings: Configure Maven settings.

mod config build maven arguments

Configure Maven build arguments.

Build arguments are added to the end of the Maven command line when building LSTs.

Usage

mod config build maven arguments [parameters] [subcommands]

Subcommands

  • delete: Removes additional build arguments for Maven.

  • edit: Configure Maven build arguments.

  • show: Displays the configured Maven additional build arguments.

mod config build maven arguments delete

Removes additional build arguments for Maven.

Usage

mod config build maven arguments delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven arguments edit

Configure Maven build arguments.

Build arguments are added to the end of the Maven command line when building LSTs.

Usage

mod config build maven arguments edit [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven arguments show

Displays the configured Maven additional build arguments.

Usage

mod config build maven arguments show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven settings

Configure Maven settings.

Allows you to specify the location of a Maven settings.xml file that should be used when Maven is being used to resolve recipe dependencies or run recipes. You can also use an environment variable that points to location of the file with ${ENV_VAR} syntax.

Usage

mod config build maven settings [parameters] [subcommands]

Examples

mod config build maven settings edit <path-to-settings.xml>

Subcommands

  • delete: Removes the configured Maven settings.

  • edit: Configure Maven settings.

  • show: Displays the configured Maven settings.

mod config build maven settings delete

Removes the configured Maven settings.

Usage

mod config build maven settings delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven settings edit

Configure Maven settings.

Allows you to specify the location of a Maven settings.xml file that should be used when Maven is being used to resolve recipe dependencies or run recipes.

Usage

mod config build maven settings edit [parameters]

Examples

mod config build maven settings edit <path-to-settings.xml>

Parameters

NameDescription

settingsXml

The location of a Maven settings.xml file to use.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config build maven settings show

Displays the configured Maven settings.

Usage

mod config build maven settings show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config environment

The build environment that the CLI is running in.

Will output information about the environment the CLI is running in (e.g., a local developer machine vs. Gitlab CI).

Usage

mod config environment [parameters] [subcommands]

Subcommands

  • show: The build environment that the CLI is running in.

mod config environment show

The build environment that the CLI is running in.

Will output information about the environment the CLI is running in (e.g., a local developer machine vs. Gitlab CI).

Usage

mod config environment show [parameters]

mod config features

Configures experimental features.

Experimental features are not guaranteed to be stable and may change in future releases.

Usage

mod config features [parameters] [subcommands]

Subcommands

  • index-recipes

mod config features index-recipes

Index recipes to avoid classloading expense on every repository. This experimental feature does not change the command line for running a recipe, but since recipes are instantiated differently, is considered experimental initially.

Usage

mod config features index-recipes [parameters]

Options

NameDescription

--enabled

mod config http

Configures HTTP options that will be used throughout the CLI.

All subsequent commands will use these settings.

Usage

mod config http [parameters] [subcommands]

Subcommands

  • proxy: Configures HTTP proxy settings that will be used for every HTTP request.

  • trust-store: Configures truststore options that will be used throughout the CLI.

mod config http proxy

Configures HTTP proxy settings that will be used for every HTTP request.

All subsequent commands will use these settings.

Usage

mod config http proxy [parameters] [subcommands]

Subcommands

  • delete: Removes HTTP proxy settings from global configuration.

  • edit: Configures HTTP proxy settings that will be used for every HTTP request.

  • show: Displays the proxy settings from global configuration.

mod config http proxy delete

Removes HTTP proxy settings from global configuration.

Proxy settings will no longer be used for HTTP requests.

Usage

mod config http proxy delete [parameters]

mod config http proxy edit

Configures HTTP proxy settings that will be used for every HTTP request.

All subsequent commands will use these settings.

Usage

mod config http proxy edit [parameters]

Options

NameDescription

--host, --proxy-host

--port, --proxy-port

mod config http proxy show

Displays the proxy settings from global configuration.

Shows the currently configured proxy settings, if any.

Usage

mod config http proxy show [parameters]

mod config http trust-store

Configures truststore options that will be used throughout the CLI.

All subsequent commands will use these settings.

Usage

mod config http trust-store [parameters] [subcommands]

Subcommands

  • delete: Removes truststore settings from global configuration.

  • edit: Configures truststore options that will be used throughout the CLI.

  • show: Displays the truststore setting from global configuration.

mod config http trust-store delete

Removes truststore settings from global configuration.

Truststore settings will no longer be used for HTTP requests.

Usage

mod config http trust-store delete [parameters]

mod config http trust-store edit

Configures truststore options that will be used throughout the CLI.

All subsequent commands will use these settings.

Usage

mod config http trust-store edit [parameters] [subcommands]

Subcommands

  • system: Configures truststore to use the Operating System specific default truststore. On Mac the system trust store is accessed via the Keychain Access app. On Windows the system trust store is accessed via the Microsoft Management Console. On Linux there is no standardized trust store, so the cacerts file under ${JAVA_HOME}/lib/security/cacerts will be used.

  • file: Configures truststore to point to a file.

  • java-home: Configures truststore to use the cacerts file in ${JAVA_HOME}/lib/security/cacerts.

mod config http trust-store edit system

Configures truststore to use the Operating System specific default truststore. On Mac the system trust store is accessed via the Keychain Access app. On Windows the system trust store is accessed via the Microsoft Management Console. On Linux there is no standardized trust store, so the cacerts file under ${JAVA_HOME}/lib/security/cacerts will be used.

Usage

mod config http trust-store edit system [parameters]

Options

NameDescription

--password

The password used to access the truststore.

mod config http trust-store edit file

Configures truststore to point to a file.

All subsequent commands will use this truststore.

Usage

mod config http trust-store edit file [parameters]

Parameters

NameDescription

file

The path to the truststore file.

Options

NameDescription

--password

The password used to access the truststore.

--provider

The provider of the truststore.

--type

The type of the truststore file.

mod config http trust-store edit java-home

Configures truststore to use the cacerts file in ${JAVA_HOME}/lib/security/cacerts.

Usage

mod config http trust-store edit java-home [parameters]

mod config http trust-store show

Displays the truststore setting from global configuration.

Shows the currently configured truststore setting, if any.

Usage

mod config http trust-store show [parameters]

mod config java

Configures Java options used for building LSTs and running recipes.

Must be configured before you can run the commands that involve non-standard Java configurations.

Usage

mod config java [parameters] [subcommands]

Subcommands

  • jdk: Configures locations of JDKs that can be used by build tools.

  • options: Configures JVM options added to tools building LSTs.

  • version: Configures the JDK to use.

mod config java jdk

Configures locations of JDKs that can be used by build tools.

Must be configured before you can run the build command if JDKs are in non-standard locations.

Usage

mod config java jdk [parameters] [subcommands]

Subcommands

  • edit: Configures locations of JDKs that can be used by build tools.

  • delete: Removes the configured JDK installations. The CLI will revert to using only detectable JDKs.

  • list: Displays the detected and configured JDK installations in the order in which they will be selected, constrained by versions detected from a particular repository.

mod config java jdk edit

Configures locations of JDKs that can be used by build tools.

Must be configured before you can run the build command if JDKs are in non-standard locations.

Usage

mod config java jdk edit [parameters]

Parameters

NameDescription

javaHomes

The paths on disk where JDK installations can be found.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java jdk delete

Removes the configured JDK installations. The CLI will revert to using only detectable JDKs.

Usage

mod config java jdk delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java jdk list

Displays the detected and configured JDK installations in the order in which they will be selected, constrained by versions detected from a particular repository.

Usage

mod config java jdk list [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--named

Filter the list of JDKs to .

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java options

Configures JVM options added to tools building LSTs.

Must be configured before you can run the build command if non-standard VM options are required.

Usage

mod config java options [parameters] [subcommands]

Subcommands

  • edit: Configures JVM options added to tools building LSTs.

  • delete: Removes configured JVM options. The CLI will no longer use custom JVM options.

  • show: Displays the configured JVM options.

mod config java options edit

Configures JVM options added to tools building LSTs.

Must be configured before you can run the build command if non-standard VM options are required.

Usage

mod config java options edit [parameters]

Examples

mod config java options edit "\-Xmx4G"

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java options delete

Removes configured JVM options. The CLI will no longer use custom JVM options.

Usage

mod config java options delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java options show

Displays the configured JVM options.

Usage

mod config java options show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java version

Configures the JDK to use.

Configure a name like "17", "17-tem", or "17.0.6-tem" depending on the degree of control needed.

Usage

mod config java version [parameters] [subcommands]

Subcommands

  • edit: Configures the JDK to use.

  • delete: Reverts to auto-detection of a JDK to use when building a repository.

  • show: Displays the configured JDK version.

mod config java version edit

Configures the JDK to use.

Configure a name like "17", "17-tem", or "17.0.6-tem" depending on the degree of control needed.

Usage

mod config java version edit [parameters]

Examples

mod config java version edit "17-tem"

Parameters

NameDescription

selectedJdk

The named JDK to use. If set to "auto", the CLI will revert to detecting the correct JDK to use from signals available in the repository.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java version delete

Reverts to auto-detection of a JDK to use when building a repository.

Usage

mod config java version delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config java version show

Displays the configured JDK version.

Usage

mod config java version show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config license

Configure a license key.

A license key allows for running recipes on private repositories without a connection to a Moderne tenant.

Usage

mod config license [parameters] [subcommands]

Subcommands

  • delete: Removes the configured license key.

  • edit: Configure the active user.

  • show: Displays information about the configured license key.

mod config license delete

Removes the configured license key.

Usage

mod config license delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config license edit

Configure the active user.

A license key allows for running recipes on private repositories without a connection to a Moderne tenant.

Usage

mod config license edit [parameters]

Parameters

NameDescription

license

The license key, provided by Moderne support.

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config license show

Displays information about the configured license key.

Usage

mod config license show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config lsts

Configures LSTs production and publishing.

Must be configured before you can run the publish command.

Usage

mod config lsts [parameters] [subcommands]

Subcommands

  • artifacts: Configures the storage layer for LSTs to be published to and downloaded from.

mod config lsts artifacts

Configures the storage layer for LSTs to be published to and downloaded from.

Must be configured before you can run the publish command.

Usage

mod config lsts artifacts [parameters] [subcommands]

Subcommands

  • artifactory: Configures the Artifactory repository that LSTs will be published to and downloaded from.

  • show: Displays the LST artifacts repository configuration.

  • maven: Configures a Maven-formatted artifact repository that LSTs will be published to and downloaded from.

mod config lsts artifacts artifactory

Configures the Artifactory repository that LSTs will be published to and downloaded from.

All subsequent publish and download commands will use this Artifactory repository.

Usage

mod config lsts artifacts artifactory [parameters] [subcommands]

Subcommands

  • edit: Configures the repository that LSTs will be published to and downloaded from. Must be configured before you can run the publish command.

  • delete: Removes the Artifactory repository configuration. The publish command will no longer function until another artifact source is configured.

  • show: Displays the Artifactory repository configuration.

mod config lsts artifacts artifactory edit

Configures the repository that LSTs will be published to and downloaded from. Must be configured before you can run the publish command.

All subsequent publish and download commands will use this artifact repository.

Usage

mod config lsts artifacts artifactory edit [parameters]

Examples

mod config lsts artifacts edit <artifact-repository-url> --user <user> --password <password>

Parameters

NameDescription

url

The URL of the artifact repository that LSTs will be published to.

Options

NameDescriptionExample

--authorization

The authorization header value to use.

Bearer XXXXX

--jfrog-api-token

The JFrog API token to use.

--local

Configuration relevant to a specific group of repositories.

--password

The password to authenticate with.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

--skip-ssl

If this parameter is included, SSL verification will be skipped.

--user

The user to authenticate with.

mod config lsts artifacts artifactory delete

Removes the Artifactory repository configuration. The publish command will no longer function until another artifact source is configured.

Usage

mod config lsts artifacts artifactory delete [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config lsts artifacts artifactory show

Displays the Artifactory repository configuration.

Usage

mod config lsts artifacts artifactory show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config lsts artifacts show

Displays the LST artifacts repository configuration.

Usage

mod config lsts artifacts show [parameters]

Options

NameDescriptionExample

--local

Configuration relevant to a specific group of repositories.

--repository-branch

Restricts the command to only run against repositories that are currently on this branch.

main

--repository-origin

Restricts the command to only run against repositories that have an origin that matches this. Supports partial matches (e.g., if the origin is git@github.com:foo/bar - all of the following would match this: github.com:foo/bar, github.com, foo, and foo/bar).

github.com

--repository-path

Restricts the command to only run against repositories that have a path (a combination of the organization/project and the repository name) that matches this. Supports partial matches (e.g., if the repository is in the foo organization and is called bar - all of the following would match this: foo/bar, foo/.*, foo, and bar).

openrewrite/rewrite

--save

When applied to a group of repositories, indicates that the configuration should be placed in a .modernecfg which can be committed to source control. When applied to global configuration, this option has no effect.

mod config lsts artifacts maven

Configures a Maven-formatted artifact repository that LSTs will be published to and downloaded from.

All subsequent publish and download commands will use this Maven repository.

Usage

mod config lsts artifacts maven [parameters] [subcommands]

Subcommands

  • edit: Configures the repository that LSTs will be published to and downloaded from. Must be configured before you can run the publish command.

  • delete: Removes the Maven artifact repository repository configuration. The publish command will no longer function until another artifact source is configured.

  • show: Displays the Maven artifact repository repository configuration.

mod config lsts artifacts maven edit

Configures the repository that LSTs will be published to and downloaded from. Must be configured before you can run the publish command.

All subsequent publish and download commands will use this artifact repository.

Usage