Maven Errors - Few common Maven error and troubleshooting part 1


In this post i am going to talk about maven build troubleshooting, Here is the list few maven error and its troubleshooting.

Tag Already exist

If you see following type of error in your release build after the perform step

 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project : Unable to tag SCM
[ERROR] Provider message:
[ERROR] The git-tag command failed.
[ERROR] Command output:

[ERROR] fatal: tag '<some tag>' already exists

Usually this means that tag already exist for same release and same tag can not be created. There could be several reasons for same.
  • manual tag was created.
  • Last release build failed after tag creation.
  • You are trying to release same version again.

    • Solution

    • You may delete the tag and rerun the build if tag was created my mistake.
    • Increase the version of your release and run the build.



Non Release dependency

If you see following type of error in your release build.

 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project: Can't release project due to non released dependencies :


 This means, Project has SNAOSHOP dependency in the pom, You can not release your project if it has snapshot artifact dependency of other project. Your Project should always point to release artifact as dependency.

Solution


  • Either release the other project first and use its latest released artifact in your dependency
OR
  • Use the already releases version of the artifact in your project.



Artifact already exist in maven repo-

Return code is: 400, ReasonPhrase:Bad Request


If you see following type of error in your release build

 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project : Failed to deploy artifacts: Could not transfer artifact  from/to release (http://maven.com/content/repositories/releases/): Failed to transfer file: . Return code is: 400, ReasonPhrase:Bad Request. -> [Help 1]

This means jar (which version) is already present in the maven repo and you are trying to release or upload same released/uploaded version again. There could be several reasons for same.
  • You are trying to perform same release again.
  • By mistake it was uploaded (somehow).
  • Previous release was bad and you want to stick to same version due to some external dependency.

Solution

According to the reasons you need to work on solution
  • You are trying to perform same release again.
    • Increase the version number and go ahead with new release.
  • By mistake it was uploaded (somehow).
    • Either you can increase the version and go ahead with new release or seek help from us to delete the old one.
  • Previous release was bad and you want to stick to same version due to some external dependency.
    • Delete the old one from maven repo.


Do not have snapshot in your pom

 If you see following type of error in your release build

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on project : You don't have a SNAPSHOT project in the reactor projects list. -> [Help 1]

This means your pom does not contain the "-SNAPSHOT" in the version field, this is must to have because release plugin will take care of removing snapshot and increasing version, tagging etc. 

Solution

Add "-SNAPSHOT" in your pom in version tag.


Return code is: 401, ReasonPhrase:Unauthorized

 If you see following type of error in your build

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project : Failed to deploy artifacts: Could not transfer artifact from/to release (http://maven.com/content/repositories/releases/): Failed to transfer file: http://maven.com/content/repositories/releases/com/something.jar. Return code is: 401, ReasonPhrase:Unauthorized. -> [Help 1]

This error says that you are trying to deploy/upload version of artifact and you do not have upload access to maven repo.

Solution

On the basis of issue here are the solutions.

Either, you do not have access to upload artifact to the give maven repo.
or
You can only deploy/upload the snapshot version of the artifact to maven repo.
Release version can only be uploaded Only once. You are trying to deploy the same version again.
You may have to remove the older version of same artifact to redeploy it again with same version.




Cached in the local repository

 if you see following type of error in your release build
[ERROR] Failed to execute goal on project : Could not resolve dependencies for project com.something:jar:0.0.2-SNAPSHOT: Failure to find com.something:jar:0.0.9-SNAPSHOT in http://artifactory.com:8080/artifactory/reliease was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

This means your project is trying to download a jar which does not exist OR it is cached 
locally with the info but does not have right artifacts.

Solution
  1. Clean in the local .m2 for given jar, In above example go to ~/.m2/repository/com/something and delete the directory 0.0.9* and run the build again.
OR
  1. Please check if this artifacts exist in maven repo or not. Most probably you may have to check the existing version and point your dependency to that.

Comments

Post a Comment

Popular posts from this blog

Colour formatting - Jenkins Console

Image
Jenkins is the main CI tool used in Software industry. This is the backbone tool for all CI and CD implementation, Build - release and deployment methods. With the help of 100s of plugin available around the jenkins, We can achieve so much of automation around build process including build/deployment pipeline, notification, analysis, pre and post build action etc. Jenkins has tremendous power to perform great amount of work around the core build process. Many time we write script in pre and post build action to perform many tasks which is becoming very command and necessary for automation. But the main limitation in running shell script is that it's very difficult to make it more human readable for errors and make it fancy. Today i am going to cover some steps to make the output of shell script colour formatted. Jenkins Configuration Steps First install following jenkins plugin https://wiki.jenkins-ci.org/display/JENKINS/AnsiColor+Plugin Go to jenkins configurati...
Read more

Manage Docker images on local disk

Docker is very powerful containerization technique, and it is becoming famous in short time. People are adapting and containerizing their applications for deployment. Soon container become very heavy and consume too much of disk space, If you do not delete old images and layers you may soon run out of disk space. Here i am trying to cover the ways to regain the disk space consumed by docker images. Moving docker filesystem to bigger mount point. Usually docker keeps all temporary files related to image building and layers at /var/lib/docker This path is local to the system usually at root partition "/" . You can mount a bigger disk space and move the content of /var/lib/docker to the new mount location and make sym link.  This way even docker images occupy space, will not affect  your system as it will be using some other mount location. Remove Old docker images Here are few ways to remove old and unused docker images Removing stopped contai...
Read more

How to migrate Parent pom from maven to gradle

Convert Maven parent/super pom to Gradle init file When you think of moving to gradle for some reason from maven, You need to take care of lot of stuff around it, You can find lot of tools and help to convert maven pom.xml to gradle build.gradle But one of the most important task as an engineer or architect would be to convert your super pom (or parent pom) in to gradle init scripts. Gradle init script provides same functionality as Maven super/parent pom. The basic difference is that you can call init script Run time As many as of them This gives us flexibility to change the init script on run time but doubt of not tracking the changes.
Read more