Error "The goal you specified requires a project to execute but there is no POM in this directory" after executing maven command

Question

I have a pom.xml in C:\Users\AArmijos\Desktop\Factura Electronica\MIyT\componentes-1.0.4\sources\pom.xml and I executed:

mvn install:install-file -DgroupId=es.mityc.jumbo.adsi -DartifactId=xmlsec-1.4.2-ADSI -Dversion=1.0 -Dpackaging=jar -Dfile=C:\Users\AArmijos\Desktop\Factura Electronica\MIyT\componentes-1.0.4\core\xmlsec-1.4.2-ADSI-1.0.jar

however it returned the error below:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.310s
[INFO] Finished at: Thu May 02 16:48:29 COT 2013
[INFO] Final Memory: 2M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] The goal you specified requires a project to execute but there is no POM
 in this directory (C:\Users\AArmijos). Please verify you invoked Maven from the
 correct directory. -> [Help 1]

Can someone explain why it fails?

Did you check here? http://maven.apache.org/plugins/maven-install-plugin/usage.html your template appears to be invalid. I see that .jar file come at first argument. — Deividi Cavarzan, May 02 '13 at 22:07
yes, this command is run correctly on another pc but I can not on my pc, I installed the latest version of jdk and maven — Adrian, May 02 '13 at 22:22
Ok now I see the error better. Do you have a pom.xml in this folder that you call mvn install-install-file? If you have, can you update your question? — Deividi Cavarzan, May 02 '13 at 22:25
putting every parameter in side double qoute resolved my issue. — rajeev pani.., Sep 14 '18 at 08:33

score 276 · Accepted Answer · edited May 23 '17 at 12:02

276

This link helped: https://stackoverflow.com/a/11199865/1307104

I edit my command by adding quotes for every parameter like this:

mvn install:install-file "-DgroupId=org.mozilla" "-DartifactId=jss" "-Dversion=4.2.5" "-Dpackaging=jar" "-Dfile=C:\Users\AArmijos\workspace\componentes-1.0.4\deps\jss-4.2.5.jar"

It's worked.

edited May 23 '17 at 12:02

Community

1
1

answered May 02 '13 at 23:01

Adrian

7,745
5
28
28

4

Since when do I need quotes? I am so puzzled right now, and relieved to finally find an answer to such a rubbish error message ... – BAERUS Jan 04 '18 at 19:50
I faced similar issue when doing `deploy:deploy-file`, but my issue was I just missed the dash ("`-`") in front of one of the options. – RAM237 Jun 04 '18 at 17:01
3

If you're in powershell, you can visually see how PowerShell is separating arguments with the colors on the command line, or by putting "echo" in front of the command. Like, "echo mvn install:install-file...". – turiyag Dec 02 '18 at 22:47
1

In earlier version of maven, I never used to provide the double-quotes. But, now it doesn't work without it. this solved my issue. – Pankaj Dec 22 '19 at 05:40
1

This happens due to having spaces in the folder paths. Adding quotes solves the issue or you can just rename the folders having spaces with under-scores or something. – Vidura Yashan Jan 27 '20 at 03:59

score 73 · Answer 2 · answered Aug 19 '15 at 00:45

73

For any of those who are experiencing this on Windows and none of the above worked, try running this from cmd.exe. Executing these commands via PowerShell caused the install to fail each time.

answered Aug 19 '15 at 00:45

Josh Sullivan

1,066
9
11

2

Same issue, Powershell and CMD argument handling work differently and seem to be confusing MVN – eageranalyst Sep 08 '15 at 22:22
1

Was following Maven's Getting Started guide and trying to execute "mvn -B archetype:generate ....." on Windows PowerShell and was getting similar error. Switching to different command line client (mintty git bash) solved the problem. – AbstractVoid Oct 21 '18 at 16:24
3

In PowerShell the `.` operator is significant because it's used for object property/method access as with most other .NET languages. If you have dots in the args generally I've quoted these in the past in order to get PowerShell to treat them as literal strings. – jpierson Dec 08 '20 at 15:50

score 62 · Answer 3 · edited Dec 08 '20 at 15:51

62

On Windows when you are using PowerShell you have to enclose all parameters with quotes.

So if you want to create a maven webapp archetype you would do as follows:

Prerequisites:

Make sure you have maven installed and have it in your PATH environment variable.

Howto:

Open windows powershell
mkdir MyWebApp
cd MyWebApp
mvn archetype:generate "-DgroupId=com.javan.dev" "-DartifactId=MyWebApp" "-DarchetypeArtifactId=maven-archetype-webapp" "-DinteractiveMode=false"

Note: This is tested only on windows 10 powershell

edited Dec 08 '20 at 15:51

jpierson

16,435
14
105
149

answered Oct 20 '17 at 08:56

J.Javan

813
8
9

Verified on Mac OS X. Also, for dprowizard `java-simple` you can use the following command: `mvn archetype:generate "-DarchetypeGroupId=io.dropwizard.archetypes" "-DarchetypeArtifactId=java-simple"` with interactive mode or with extra parameters. – Andrey Lebedenko Jul 25 '18 at 14:45
same problem exists also on command prompt. enclosing parameter values within quotes is the real solution. – Gautam Dec 27 '21 at 05:44

score 16 · Answer 4 · answered Mar 22 '17 at 05:33

16

Adding one more answer for Windows users. If none of this solves the problems.

Do not add space before or after =

-DgroupId= com.company.module //Wrong , Watch the space after the equal to 
-DgroupId=com.company.module //Right

Its better to put everything inside double quotes, like "-DgroupId=com.." This will give you exact error rather than some random error.

Weird that , maven does not even care to mention this in the documentation.

answered Mar 22 '17 at 05:33

madhairsilence

3,787
2
35
76

3

your solution worked , I put all the -D section within ""... it's really amazing that product so poorly engineered and ill-coded like Maven has managed to become so popular... – Pierluigi Vernetto Jul 22 '17 at 14:54

score 9 · Answer 5 · answered Feb 07 '18 at 07:57

9

In my case, its because I copied pasted the command from the browser and it turned out that the dash was not the ASCII dash, just delete and type the dash again.

http://www.toptip.ca/2017/04/maven-most-weird-error-causing-failure.html

answered Feb 07 '18 at 07:57

Mideel

801
7
16

score 6 · Answer 6 · edited May 03 '23 at 08:24

Totally true. When using PowerShell, you need to put quotes.
I run the command and put quotes around the parameters that have a dot, this works.
Instead of typing 1.4, you should type "1.4".

First time:

mvn archetype:generate 
   -DgroupId=com.mycompany.app 
   -DartifactId=my-app 
   -DarchetypeArtifactId=maven-archetype-quickstart 
   -DarchetypeVersion=1.4 -DinteractiveMode=false

Error:
[ERROR] The goal you specified requires a project to execute 
but there is no POM in this directory 
(C:\Users\jcrojas\OneDrive - Superfinanciera\Personal\Aprendizaje\Maven\test). 
Please verify you invoked Maven from the correct directory. -> [Help 1]

Second time:

mvn archetype:generate 
   -DgroupId=**"com.mycompany.app"** 
   -DartifactId=my-app 
   -DarchetypeArtifactId=maven-archetype-quickstart 
   -DarchetypeVersion=**"1.4"** 
   -DinteractiveMode=false

...BUILD SUCCESS...

The command also works if it is run with the Windows command line, CMD.
In this case, the quotation marks are not necessary.

Thanks Juan. Your double quotes one tip helped me to solve my issue. — abdeali004, Jan 15 '23 at 06:28

score 4 · Answer 7 · answered Dec 27 '21 at 05:41

I was trying to install java jms-1.1.jar after downloading a copy from jboss repository.

Encountered exact same error and specifically on windows. Tried everything i.e. changed maven version / jdk version but no avail.

I was using the command below .

mvn install:install-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar -Dfile=jms-1.1.jar

Finally took a que from the comment in the main question and put every parameter value within double quotes

mvn install:install-file -DgroupId="javax.jms" -DartifactId="jms" -Dversion="1.1" -Dpackaging="jar" -Dfile="jms-1.1.jar"

This solved the problem. The issue seems very specific to windows environment. On ubuntu and mac the command works without any issues.

Some other answers and posts suggest to use a variation of the jar from apache but since the artifact ids are different its not really a solution. — Gautam, Dec 27 '21 at 05:42

score 1 · Answer 8 · answered Sep 12 '15 at 06:58

1

Changing mvn clean to mvn clean --file *.pom fixed this issue for me.

answered Sep 12 '15 at 06:58

Matthias Braun

32,039
22
142
171

score 1 · Answer 9 · answered Oct 27 '15 at 23:41

1

On Windows, I got this error when running under a non-administrator command prompt. When I ran this as administrator, the error went away.

answered Oct 27 '15 at 23:41

tcb

4,408
5
34
51

Potentially you were running non-administrator under PowerShell and CMD for administrator so that the real difference was whether it was being run in PowerShell or not. – jpierson Dec 08 '20 at 15:54

score 1 · Answer 10 · answered Aug 04 '16 at 14:46

1.create a lib folder in your project file,

2.copy your jarFiles to the lib folder

3.right click on to your jarFile go to build path>Add to build path (now your jar file is part of your refrerenced libraries )

4.open command prompt and navigate to your project directory and write

mvn install: install-file "-Dfile=<yourJarFileName>.jar" "-DgroupId=<yourGroupID>" "-DartifactId=<yourArtifactId>" "-Dversion=<yourVersion>" "-Dpackaging=jar"

6.Rebuild your local repository index by opening in eclipse- go to window>show view>other>maven>maven Repositories. Right click on local Repositores and hit "RebuildIndex"

5.open your pom.xml file and add your dependency

    <dependency>
        <groupId><yourGroupID></groupId>
        <artifactId><yourArtifactId></artifactId>
        <version><yourVersion></version>
    </dependency>

and run

mvn clean
mvn compile 
mvn test

I've been wondering how a simple maven command would be failing... I came up with your solution and voila! It worked! Nobody was writing the java params within the ", which was what I was missing. Thank you very much :) — joninx, Sep 26 '16 at 14:21

score 0 · Answer 11 · edited May 23 '17 at 12:26

I got this error suddenly in Netbeans (but it worked from the command line) and it turns out some other program had changed the default directory of the command prompt. And because Netbeans runs "cmd /c" when invoking maven, it starts in an incorrect directory.

Check out in Regedit the value for

HKEY_CURRENT_USER\Software\Microsoft\Command Processor\Autorun

If it has been set, you probably should remove it to fix the problem. (1)

(I landed here when trying to resolve this issue, might not be 100% applicable to the current question - but might help others)

(1) Changing default startup directory for command prompt in Windows 7

score 0 · Answer 12 · answered Oct 20 '17 at 11:00

The execution of maven command required pom.xml file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects.
Make sure that porject should contains pom.xml at the root level.

Prabu Balasubramanian · Answer 13 · 2018-07-17T06:57:15.970

Add the Jenkinsfile where the pom.xml file has present. Provide the directory path on dir('project-dir'),

Ex:

node {

    withMaven(maven:'maven') {

        stage('Checkout') {
            git url: 'http://xxxxxxx/gitlab/root/XXX.git', credentialsId: 'xxxxx', branch: 'xxx'
        }

        stage('Build') {

            **dir('project-dir') {**
                sh 'mvn clean install'

                def pom = readMavenPom file:'pom.xml'

                print pom.version
                env.version = pom.version
            }
        }
    }
}

score 0 · Answer 14 · answered Jul 15 '20 at 07:11

There may be a problem with Maven path configuration, if you used unix-like Operator System.

step 1: create new file in path ~/.bash_profile

JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home
CLASSPAHT=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
PATH=$JAVA_HOME/bin:$PATH:
export JAVA_HOME
export CLASSPATH
export PATH

step 2: shell run source ~/.bash_profile OR modify zsh config file(add new line: source ~/.bash_profile)

score 0 · Answer 15 · answered Dec 27 '20 at 11:49

0

Just watch out for any spaces or errors in your arguments/command. The mvn error message may not be so descriptive but I have realised, usually spaces/omissions can also cause that error.

answered Dec 27 '20 at 11:49

Arthur

568
7
17

score 0 · Answer 16 · answered Jul 26 '22 at 15:56

0

I just added the path to the pom.xml as such mvn -f path/to/pom.xml <goals> ... Worked great for me

answered Jul 26 '22 at 15:56

Cesar Arnouk

25
6

score 0 · Answer 17 · answered Aug 22 '22 at 10:24

0

There could be some special characters added to your command like the '-' U+2013 and U+002d

Please remove the special characters and try the command

answered Aug 22 '22 at 10:24

user3865770

405
1
6
13

score -1 · Answer 18 · answered Mar 30 '16 at 17:39

-1

"The goal you specified requires a project to execute": The answer is in your question. I faced the same issue. Run the "mvn command" within the project folder, Also make sure sure its a maven configured project and hence contains the "POM.xml" file and you should be good to go!

answered Mar 30 '16 at 17:39

krutika sheth

15
2

2

This command is to install local 3rd party jar. We dont have the project source code with us – madhairsilence Mar 22 '17 at 05:27

score -1 · Answer 19 · answered Apr 13 '20 at 06:33

-1

Check for the name of the file, i.e pom.xml file is spelled correctly with proper file extension .xml.

Example for this error are

pom.ml pm.xl

answered Apr 13 '20 at 06:33

Gani

422
1
8
16

score -3 · Answer 20 · answered Jan 28 '14 at 00:46

-3

Please run it from the directory where POM.XML resides.

answered Jan 28 '14 at 00:46

Sasiraj

107
1
1

9

Downvoted because the `install:install-file` goal doesn't need to be (can't?) run on a project. It's used for manually installing an artifact into a repository. – Zoltán Aug 06 '14 at 15:31
I am trying to upload a zip file that has no Pom xml. downvoted – kazanaki Apr 28 '15 at 11:30

Error "The goal you specified requires a project to execute but there is no POM in this directory" after executing maven command

20 Answers20

First time:

Second time:

Linked