How to Skip Tests When Packaging a Maven Project

Hello, I am a senior architect. In everyday development we mainly write code, and packaging a project is not difficult.

The simplest way to package is to use the Maven plugin, which creates a JAR that can be run with java -jar xx.jar.

When the production database is inaccessible, the default Maven test phase blocks packaging because tests cannot run; therefore we need to skip tests.

Maven’s default lifecycle has 23 phases, and the package phase depends on the preceding test phase, which must succeed before packaging occurs.

1. Command‑line way to skip tests

You can add skip flags to the Maven command:

mvn package -DskipTests=true

-DskipTests=true

skips test execution but still compiles test classes into target/test-classes.

mvn package -Dmaven.test.skip=true

-Dmaven.test.skip=true

skips both test execution and compilation of test classes.

During mvn package, Maven runs tests in src/test/java using JUnit; the two flags control whether tests are executed or compiled.

2. Configure pom.xml to skip tests

Add the following plugin configuration to your pom.xml:

<build>
  <plugins>
    <!-- maven skip tests during packaging -->
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-surefire-plugin</artifactId>
      <configuration>
        <skip>true</skip>
      </configuration>
    </plugin>
  </plugins>
</build>

3. Direct IDE configuration

In the Maven tool window, click the “Skip Tests” icon and then run the “Package” lifecycle; the build will skip tests.

4. Add Maven parameters in IDE settings

Open

Build → Execution → Deployment → Maven Tools → Maven → Runner

and add -Dmaven.test.skip=true or -DskipTests=true to the VM options to skip tests during packaging.

5. Change settings to enable “Skip Test”

In the same Maven Runner properties, check the “Skip Test” option.

These are the main ways to skip tests when packaging a Maven project.