Error when creating a new maven project

Question

When I try create a new maven project (with several archetypes, not only the one below), I am facing this error:

Unable to create project from archetype [org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE]
Unable to add module to the current project as it is not of packaging type 'pom'

Anyone know why this is happening, and how to solve it?

but i don't have a project yet (I am trying create one). what pom.xml i should modify? — Kleber Mota, Apr 22 '14 at 10:58
Be sure to spell all the options correctly. A misspelling is what brought me here. — Marvo, Jul 22 '20 at 18:52

score 33 · Accepted Answer · answered Apr 22 '14 at 11:37

It seems that your directory is not empty. this command line works for me: (in an empty directory)

mvn archetype:generate -DgroupId=fr.myGroupId -DartifactId=MyApplication -Dpackagename=fr.myGroupId -DarchetypeArtifactId=maven-archetype-quickstart

the result is:

[INFO] Using property: groupId = fr.myGroupId
[INFO] Using property: artifactId = MyApplication
Define value for property 'version':  1.0-SNAPSHOT: : 
[INFO] Using property: package = fr.myGroupId
Confirm properties configuration:
groupId: fr.myGroupId
artifactId: MyApplication2
version: 1.0-SNAPSHOT
package: fr.myGroupId
 Y: : 
[INFO] ----------------------------------------------------------------------------
[INFO] Using following parameters for creating project from Old (1.x) Archetype: maven-archetype-quickstart:1.0
[INFO] ----------------------------------------------------------------------------
[INFO] Parameter: groupId, Value: fr.myGroupId
[INFO] Parameter: packageName, Value: fr.myGroupId
[INFO] Parameter: package, Value: fr.myGroupId
[INFO] Parameter: artifactId, Value: MyApplication2
[INFO] Parameter: basedir, Value: /home/ABC-OBJECTIF/philippe.demanget/workspace/pdemanget/tmp/mvn
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] project created from Old (1.x) Archetype in dir: /home/ABC-OBJECTIF/philippe.demanget/workspace/pdemanget/tmp/mvn/MyApplication2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9.764s
[INFO] Finished at: Tue Apr 22 13:35:17 CEST 2014
[INFO] Final Memory: 14M/216M
[INFO] ------------------------------------------------------------------------

I can reproduce your error by doing this command line inside the newly created directory:

cd MyApplication
mvn archetype:create -DgroupId=fr.myGroupId -DartifactId=MyApplication -Dpackagename=fr.myGroupId -DarchetypeArtifactId=maven-archetype-quickstart
[...] [INFO] BUILD FAILURE

It don't need to be empty, it just need there is no `pom.xml` in current dir, otherwise current dir will be thought as the parent project, and their packing type need to match — Eric, Aug 21 '16 at 15:41
Bump into the same error with maven 3.6.0 and I am sure the directory is empty. — Kok How Teh, Nov 05 '18 at 03:08
@KokHowTeh I also have the same issue as you and am on Maven 3.6.0. Trying to create new Maven package, keep giving me the error that "... it is not of packaging type 'pom'." — Jessica, Jun 06 '19 at 17:05

score 23 · Answer 2 · edited Dec 17 '15 at 14:50

23

I got the same issue, solved by manually removing a unused pom.xml file at the root of workspace directory

edited Dec 17 '15 at 14:50

Tomasz Jakub Rup

10,502
7
48
49

answered Dec 17 '15 at 14:40

Florent Barreau

230
2
4

1

This is exact the issue I got, a `pom.xml` from where I execute the command cause the issue, and issue fixed after remove the file. Probably it's because `mvn` though the current dir is an parent project when there is a `pom.xml` file, and the packing type from the pom.xml is different from what is specified in the command. – Eric Aug 21 '16 at 15:40
Holy crap, I spent like three hours trying to figure out my issue. I just removed the ```pom.xml``` like you said and it worked. – Jessica Jun 06 '19 at 17:06

score 5 · Answer 3 · answered Feb 13 '19 at 16:47

You have to remove the already existing pom.xml or if you need it to execute the maven command, try adding <packaging>pom</packaging> to your pom.

Since if you have an already existing in the current directory, it should match with the package structure. It is always to good to start with no pom file in the parent directory.

This should work.

score 4 · Answer 4 · answered Dec 14 '19 at 19:45

4

I was having the same problem using Windows PowerShell in a newly created directory with nothing in it. I tried the command using the regular Windows Command Prompt, and it worked fine.

answered Dec 14 '19 at 19:45

Jonathan

41
2

I actually didn't need a newly created directory. Thanks, @Jonathan – Tien Dec 18 '20 at 06:14

score 0 · Answer 5 · answered Aug 27 '22 at 05:42

0

I simply created new workspace and it worked for me..

answered Aug 27 '22 at 05:42

Hariom Kumar

1
1

Error when creating a new maven project

5 Answers5

Linked