Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6935111
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T12:03:34+00:00 2026-05-27T12:03:34+00:00

I am using maven-release-plugin on a multi-module project with the following layout: ROOT/ +

  • 0

I am using maven-release-plugin on a multi-module project with the following layout:

ROOT/
  + parent
  + module1
  + module2

In the parent‘s pom, the child modules configured using modules element. Each one of the projects are configured to use the plugin with basic configuration and a tag base for each. I have the following problems:

  • When I run mvn release:prepare on parent, after the line that says Checking for snapshot dependencies ..., I receive no prompt to enter the versions. If I press Enter for the number of questions it requires answer, it continues. Why do not I receive prompts on the screen? (The same thing happens if run with -DdryRun=true)

  • After running mvn release:prepare (with or without -DdryRun=true), the release:prepare is SKIPPED for the child modules.

I am using the basic configuration on the plugin’s guide. I’d be thankful for any ideas or clues of what’s wrong.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T12:03:34+00:00Added an answer on May 27, 2026 at 12:03 pm

    Regarding the lack of prompts, are you running mvn through a pipe? This happened to me when I was using a script to do colour highlighting of Maven’s log output, because Maven doesn’t output a newline after the prompt.

    By the way, you may be able to use mvn’s -B option to run in batch mode; maven-release-plugin will use the default values instead of prompting.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to perform a release using a multi-module maven project. My objective
i would like to release a snapshot project 'foo-1.0-SNAPSHOT' using the maven release plugin.
Im using maven to build a multi module project. But some projects are in
I am trying to release a web project using Maven 2.2.1 and the maven-release-plugin
I'm using the maven release plugin on hudson. I'm trying to release the project.
We're using a standard svn layout (/branches/x.y, /tags, /trunk) and mvn release (i.e. maven-release-plugin)
When using the maven-release-plugin with Git, mvn release:prepare happily tags the release in the
I am using the maven release plugin. Problem is simple: I don't want to
We have a multi module project with following modules: Database Persistence Business Application The
I'm using the maven release plugin on hudson with autoVersionSubmodules set to true to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.