How can I get maven-release-plugin to skip my tests?

Question

How can I get the maven-release-plugin to run without triggering the tests?

I have tried

-Dmaven.test.skip=true

and

-DskipTests

and

-DpreparationGoals=clean

...yet none work.

Yes, I know I shouldn't release if the tests don't pass, but I don't have control over making my coworkers write reliable tests.

score 413 · Answer 1 · edited Jan 31 '14 at 15:39

413

-Darguments="-DskipTests" is what you want, or explicitly configuring the forked executions in the pom.

edited Jan 31 '14 at 15:39

Grzegorz Rożniecki

27,415
11
90
112

answered Dec 31 '11 at 00:03

bmargulies

97,814
39
186
310

1

It works for me, thanks and +1 but ... Wny is this necessary? – javamonkey79 Oct 10 '12 at 17:13
5

IT is necessary because the release process forks a new maven process, and the tpical -DskipTests are not passed along as system properties. – Eddie Dec 03 '12 at 19:18
4

wish I could vote you `2` up. I spent hours trying to get this right... but 1. Did I miss something in the documentation or is the mvn documentation missing something ? 2. I had `true` configured in my company POM. Still did not work. What worked was your solution. – Pulak Agrawal Dec 11 '12 at 12:24
Do you need some specific config in the pom to make this work? – DenCowboy Jun 14 '18 at 13:19

score 42 · Answer 2 · edited Feb 08 '13 at 18:55

-Darguments="..." passes arguments to the forked maven process, but it is important to realise that there are two different switches being used here. The -DskipTests forces maven to not run any tests, but the tests are still compiled (this is important if you have any dependencies on a test-jar type). The -Dmaven.test.skip=true forces maven to not even compile the tests, which means that any test-jars will not be generated.

So, you must use -Darguments, but to skip tests running use only skipTests, to stop them compiling use maven.test.skip.

score 21 · Answer 3 · edited Sep 26 '12 at 06:30

21

If you just want to skip integration tests, this will do it:

-Darguments="-DskipITs"

edited Sep 26 '12 at 06:30

Mihai Iorga

39,330
16
106
107

answered Sep 24 '12 at 03:27

David Gilks

319
2
3

idriss Eliguene · Answer 4 · 2019-04-18T07:07:35.590

you have too differents choices to avoid and skip tests with the release plugin

The first is to pass as argument on cli to the release goal or phases by providing a -Darguments:

exemple: mvn -X -Darguments="-Dmaven.javadoc.skip=true -Dmaven.test.skipTests=true -Dmaven.test.skip=true" -P release-mode release:prepare

-The second is to perform thoses arguments on your pom.xml in the build like this:

<plugin>    
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-release-plugin</artifactId>
                <dependencies>
                    <dependency>
                        <groupId>org.apache.maven.scm</groupId>
                        <artifactId>maven-scm-provider-gitexe</artifactId>
                        <version>1.9.4</version>
                    </dependency>
                </dependencies>
                <configuration>
                    <skip>true</skip>
                    <skipTests>true</skipTests>
                    <preparationGoals>clean validate</preparationGoals>
                    <arguments>-Dmaven.javadoc.skip=true -Dmaven.test.skipTests=true -Dmaven.test.skip=true</arguments>
                    <useReleaseProfile>false</useReleaseProfile>
                    <releaseProfiles>release-mode</releaseProfiles>
                    <tagNameFormat>TEST-@{project.version}</tagNameFormat>
                </configuration>
            </plugin>

Note that the second method override the first.

I recommanded you to prepare release first on a single action and then you can edit the release.properties file on the working directorie and look the exec.additionalArguments properties if your arguments are there. It will look like: exec.additionalArguments=-Dmaven.javadoc.skip\=true -Dmaven.test.skipTests\=true -Dmaven.test.skip\=true -P release-mode.

After you can perform the release.

score 1 · Answer 5 · answered Jul 09 '21 at 09:10

I have managed to avoid running the verify goal by simply adding the configuration preparationGoals to clean:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>2.5.3</version>
  <configuration>
    <preparationGoals>clean</preparationGoals> <!-- See here -->
  </configuration>
</plugin>

Mfuon Leonard · Answer 6 · 2020-08-27T11:01:23.823

0

Use the following argument to skip test

-Darguments="-DskipTests"

or

alternatively skipping by default

 [...]
  <properties>
    <skipTests>true</skipTests>
  </properties>
  [...]

edited Aug 27 '20 at 11:01

answered Jun 28 '16 at 07:39

Mfuon Leonard

192
4
19

2

This question is specifically about the Maven release plugin, so these are not the Maven goals that will be used. – Jaap Dec 19 '16 at 15:37

How can I get maven-release-plugin to skip my tests?

6 Answers6

Linked