How to manually install an artifact in Maven 2?

Question

I've encountered some errors when I tried to install an artifact manually with Maven 2. I wanted to install a jar from a local directory with the command

mvn install:install-file -Dfile=jta-1.0.1B.jar

But Maven gave a build error which reads like:

Invalid task '.01B.jar': you must
specify a valid lifecycle phase, or a
goal in the format plugin:goal or
pluginGroupId:pluginArtifactId:pluginVersion:goal

Is there a mistake with my command?

What is the status of this? Is you question resolved? – Matt Jun 16 '09 at 19:54 — Matt, Jun 16 '09 at 19:54

score 156 · Accepted Answer · edited Nov 28 '12 at 00:30

156

You need to indicate the groupId, the artifactId and the version for your artifact:

mvn install:install-file \
  -DgroupId=javax.transaction \
  -DartifactId=jta \
  -Dpackaging=jar \
  -Dversion=1.0.1B \
  -Dfile=jta-1.0.1B.jar \
  -DgeneratePom=true

edited Nov 28 '12 at 00:30

Charles Duffy

280,126
43
390
441

answered Jan 14 '09 at 08:06

Romain Linsolas

79,475
49
202
273

8

-Dpackaging=jar or similar is missing – kaboom Jun 05 '10 at 17:09
@kaboom No! By default, the packaging is jar, so you don't need to specify this in thé command... – Romain Linsolas Jun 05 '10 at 18:08
does not work for me too: Missing group, artifact, version, or packaging information – ahmet alp balkan Aug 04 '10 at 17:02
5

@romaintaz kaboom is correct; you need -Dpackaging=jar (or whatever the type is) otherwise you will get an error about "'packaging' is missing." – Jack Edmonds Aug 07 '10 at 01:21
3

It seems that the packaging parameter is needed except if you provide a pom file. In the latter case, the type of package is taken from the pom. – Romain Linsolas Feb 22 '11 at 11:45
+1 for `-DgeneratePom=true`. Otherwise you get warnings when using the artifact that the pom is missing. – sourcedelica Oct 10 '13 at 16:00
1

If using PowerShell, make sure you use quote likewise `"-DgroupId=javax.transaction"` – ankitjaininfo Dec 09 '13 at 18:53

Pascal Thivent · Answer 2 · 2009-03-13T23:20:18.367

According to maven's Guide to installing 3rd party JARs, the command is:

mvn install:install-file -Dfile=<path-to-file> -DgroupId=<group-id> \
-DartifactId=<artifact-id> -Dversion=<version> -Dpackaging=<packaging>

You need indeed the packaging option. This answers the original question.

Now, in your context, you are fighting with a jar provided by Sun. You should read the Coping with Sun JARs page too. There, you'll learn how to help maven to provide you better information about Sun jars location and how to add Java.net Maven 2 repository which contains jta-1.0.1B.jar. Add this in your ~~settings.xml (not portable) or~~ pom.xml (portable):

  <repositories>
    <repository>
      <id>maven2-repository.dev.java.net</id>
      <name>Java.net Repository for Maven</name>
      <url>http://download.java.net/maven/2/</url>
      <layout>default</layout>
    </repository>
  </repositories>

score 16 · Answer 3 · edited Jan 31 '19 at 20:43

16

I had to add packaging, so:

mvn install:install-file \
  -DgroupId=javax.transaction \
  -DartifactId=jta \
  -Dversion=1.0.1B \
  -Dfile=jta-1.0.1B.jar \
  -DgeneratePom=true \
  -Dpackaging=jar

edited Jan 31 '19 at 20:43

BryanH

5,826
3
34
47

answered Mar 03 '09 at 16:45

I had lots of issues installing a jar file manually, and it kept failing until I typed it this way exactly. Now it works! – gregturn Sep 28 '12 at 19:50

score 8 · Answer 4 · answered Sep 27 '10 at 11:47

8

Answer is to escape the dash!

http://www.mail-archive.com/users@maven.apache.org/msg83991.html

answered Sep 27 '10 at 11:47

S. Bollweber

81
1
1

Damm me. that was it. all the -D parameters must be enclosed in `. – Martin Oct 13 '10 at 12:02

score 4 · Answer 5 · answered May 14 '10 at 10:00

4

If you ever get similar errors when using Windows PowerShell, you should try Windows' simple command-line. I didn't find out what caused this, but PowerShell seems to interpret some of Maven's parameters.

answered May 14 '10 at 10:00

Koraktor

41,357
10
69
99

Look at S. Bollweber answer above. And at least TakeCommand expresses the same bahaviour. – Martin Oct 13 '10 at 12:08
1

No reason to downvote my answer – S. Bollweber answered a few months after myself. – Koraktor Dec 16 '10 at 22:23

score 2 · Answer 6 · answered Jan 24 '14 at 19:07

All the posted answers rightfully discuss this from a strictly maven perspective. My issues was in doing this install for maven using Netbeans as my primary IDE. I found the below article helpful.

Credit to the following netbeans forum article: http://forums.netbeans.org/topic22907.html

In Maven project open "Add dependency" dialog
Make up some groupId, artifactId and version and fill them, OK.
Dependency will be added to the pom.xml and will appear under "Libraries" node of maven project
Right-click Lib node and "manually install artifact", fill the path to the jar. Jar should be installed to local Maven repo with coordinates entered in step 2)

How to manually install an artifact in Maven 2?

6 Answers6

Linked