Why Does Maven Say My POM File Is Missing?

Article ID:204944844
1 minute readKnowledge base

Issue

The following errors will be reported in the jenkins build log:

[ERROR] The goal you specified requires a project to execute but there is no POM in this directory (D:\JENKINS-WORK\workspace\Code Quality\DS-SONAR-CASPER). Please verify you invoked Maven from the correct directory. -> [Help 1]
org.apache.maven.lifecycle.MissingProjectException: The goal you specified requires a project to execute but there is no POM in this directory (D:\JENKINS-WORK\workspace\Code Quality\DS-SONAR-CASPER). Please verify you invoked Maven from the correct directory.

The build will fail since maven will not perform a build job.

Environment

  • CloudBees Jenkins Operations Center

  • CloudBees Jenkins

Resolution

Generally the file/folder path is wrong and can be corrected by specifying the correct path. Both Windows and *nix operating systems also need to have file/folder names escaped if spaces or special characters are used in the names.

Linux Example:

Setting a path to /opt/jenkins/my workspace folder/ will fail because the spaces in between the words "my workspace" and "workspace folder" were not properly escaped.

A more correct expression would be like this:

/opt/jenkins/my\ workspace\ folder/

Windows Example:

Setting a path to C:\jenkins\my workspace folder\ will fail because the spaces in between the words "my workspace" and "workspace folder" were not properly escaped.

A more correct expression would be like this:

C:\jenkins\"my workspace folder"\