How to get a Maven release to work with git?

git maven maven-release-plugin
willCode4Beer picture willCode4Beer · Mar 25, 2011 · Viewed 14.5k times · Source

Trying to release, I always get this:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The git-commit command failed.
Command output:

There is nothing by "command output".

Is there some secret configuration trick to get maven to play nice with git?

Answer

VonC picture VonC · Mar 26, 2011

The only case I saw where the git-commit command output was empty was on issue 556, where the following solution was proposed:

I had exactly the same problem as you; and:

  • removing the release.properties and
  • putting back my pom version to a SNAPSHOT (it was previously changed by the plugin) version

resolved the problem; the process ended successfully.

Related questions

"Git fatal: ref HEAD is not a symbolic ref" while using maven release plugin

I get the following error output while running the Maven release plugin prepare step i.e. mvn release:prepare --batch-mode -DreleaseVersion=1.1.2 -DdevelopmentVersion=1.2.0-SNAPSHOT -Dtag=v1.1.2 -X from an Atlassian Bamboo plan. However doing the same in the command line works …

Read More
Maven release plugin git credentials

We are using Jenkins and just switched from a file based git repo without authentication to using GitBlit with proper authentication over http. The problem is - how is maven supposed to authenticate itself in batch mode? Updating each job …

Read More
Maven Release Plugin use in Jenkins Pipeline

I'm using Jenkins Pipeline to automatically build and deploy my Java apps. I also use maven-release-plugin to perform Maven deploy to Artifactory. The problem is my Jenkinsfile (or Jenkins Pipeline Configuration) : We commit a version 0.1.00-SNAPSHOT on release branch Jenkins …

Read More