• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

Behaviour of Maven release plugin

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I am using the maven release plugin to automate the Java projects I am working on. I have utilised the maven release plugin to update the versions of all my poms, and it have worked like a charm. However, since yesterday, I have a very strange behaviour when I am trying to update the version of all poms of my projects.  After the execution of the following command:

mvn release:update-versions -DautoVersionSubmodules=true

The usual prompt appears on the console to change the version of the pom to whatever version I want. Maven offers to change to the version 0.1.4-SNAPSHOT (as the previous version was the 0.1.3-SNAPSHOT) but I would like to change all the poms to a release version (which I have already done before) 0.1.3. When I try to do that, the prompt never advances, and it get stuck on asking me for the new version, as illustrated in the release-plugin-behaviour image (in attach).

Anyone have experienced such behaviour? as I have used it before and I know it works, I would like to hear from all of you what do you think is happening.
[Thumbnail for release-plugin-behaviour.png]
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!