DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Web App Load Testing Using Maven Plugins for Apache JMeter, and Analyzing the Results
  • Implementing a Weekly Release Cycle for Mobile Apps
  • Solid Testing Strategies for Salesforce Releases
  • Integrate Cucumber in Playwright With Java

Trending

  • How to Build an Agentic AI SRE Co-Pilot for Incident Response
  • Why Your AI Agent's Logs Aren't Earning Trust
  • Zero-Downtime Deployments for Java Apps on Kubernetes
  • Beyond Manual Annotation: Engineering Self-Correcting Pseudo-Labeling Pipelines
  1. DZone
  2. Coding
  3. Java
  4. Configuring the Maven Release Plugin to Skip Tests

Configuring the Maven Release Plugin to Skip Tests

Skipping the execution of tests during the Release plugin execution might improve your release time because the Maven Release Plugin already executes the same tests twice.

By 
Alex Soto user avatar
Alex Soto
·
Sep. 19, 16 · Opinion
Likes (2)
Comment
Save
Tweet
Share
16.2K Views

Join the DZone community and get the full member experience.

Join For Free

If you are using Maven in addition to the Maven Release Plugin, it is in your best interest to skip the execution of tests during the Release plugin execution. There are many very different reasons why you may need to do this, but it may depend on the nature of the project or how the CI pipeline is implemented.

Note that this might be able to bring a great improvement in your release time since performing the release with the Maven Release Plugin implies executing the same tests twice: once in the Prepare step and then once more in the Perform step.

If you would like to avoid executing tests in the Prepare phase, then you need to run it like so:

mvn -DpreparationGoals=clean release:prepare

If you would like to avoid executing tests during the Perform phase, then you need to run it like so:

mvn -Darguments="-Dmaven.test.skip=true" release:perform

It is important to note that I am not saying that you don't need to execute tests during the Release process. Instead, what I am saying is that this might be a good idea if your Release process doesn't fit the standard Release process of the plugin and, for example, you are already running tests before you have executed the plugin.

Release (computing) Testing Apache Maven

Published at DZone with permission of Alex Soto. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Web App Load Testing Using Maven Plugins for Apache JMeter, and Analyzing the Results
  • Implementing a Weekly Release Cycle for Mobile Apps
  • Solid Testing Strategies for Salesforce Releases
  • Integrate Cucumber in Playwright With Java

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook