--- title: '`glab dependency-firewall maven`' stage: AI Clients group: Developer Clients info: To determine the technical writer assigned to the Stage/Group associated with this page, see --- Run Maven through the GitLab Dependency Firewall. (BETA) ## Synopsis Run the Maven binary (`mvn`) through the GitLab Dependency Firewall. The command checks each package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run. The command uses your package manager's registry or index configuration, and does not modify it. The command checks `.jar`, `.pom`, `.aar`, and `.war` files, including timestamped snapshot files. It does not check checksum and signature files (`.md5`, `.sha1`, `.sha256`, `.sha512`, and `.asc`). The command runs `mvn` from your `PATH`. The Maven Wrapper (`./mvnw`) is not supported. Maven does not download artifacts already cached in `~/.m2/repository/`, so the firewall does not check them. Clear the cache to check them again. All arguments are forwarded to `mvn` verbatim. This feature is in beta and might not be ready for production use. It might be unstable and breaking changes can occur outside of major releases. For more information, see . ```plaintext glab dependency-firewall maven [flags] ``` ## Examples ```console # Build a project through the Dependency Firewall glab dependency-firewall maven verify # Resolve dependencies through the Dependency Firewall glab dependency-firewall maven dependency:resolve # Deploy a project through the Dependency Firewall glab dependency-firewall maven deploy ``` ## Environment variables ```plaintext HTTPS_PROXY: outbound proxy glab uses to reach package registries. Credentials in the URL are sent to the proxy. HTTP_PROXY: outbound proxy for plain-HTTP registries. When it's unset, glab uses HTTPS_PROXY. NO_PROXY: hosts glab reaches directly instead of through an outbound proxy. glab reads the proxy settings for maven from your user and global config files first (~/.m2/settings.xml, ${maven.home}/conf/settings.xml), so the outbound proxy can differ from HTTPS_PROXY and HTTP_PROXY. glab doesn't read proxy settings from files inside the project. glab doesn't support proxy passwords encrypted with settings-security.xml. ``` ## Options inherited from parent commands ```plaintext -h, --help Show help for this command. ```