How to resolve maven dependency explicitly from command line arguments?

Question

I have a project A which depends on artifact B. I made some hack on B, and want to see it in A. So I don't want A to use the version in my local repository, instead, I want A to use my hacked version of B.

I'm looking for a solution that can specify my-hacked-B.jar as dependency of A, like this:

cd A && mvn package -Ddependency.org.groupB.B.jar.path=path/to/my-hacked-B.jar

Is it possible, or I have to install the modified B in my local repository?

You can do this from command line: http://stackoverflow.com/questions/1776496/a-simple-command-line-to-download-a-remote-maven2-artifact-to-the-local-reposito — cwu9T9, Dec 05 '12 at 20:40

score 2 · Answer 1 · answered Dec 07 '11 at 17:17

2

You can't do it on the command line, but you can set the dependency scope to system in the pom.xml and provide a path to the dependency.

<dependency>
  <groupId>org.groupB</groupId>
  <artifactId>B</artifactId>
  <version>2.0</version>
  <scope>system</scope>
  <systemPath>${project.basedir}/path/to/hacked-B.jar</systemPath>
</dependency>

answered Dec 07 '11 at 17:17

Sean Patrick Floyd

292,901
67
465
588

Thanks. But I don't want my pom.xml to be dirty. – Yang Bo Dec 07 '11 at 17:28
@user955091 I thought so, but unfortunately that's the only way that I know of. – Sean Patrick Floyd Dec 07 '11 at 18:30

score 1 · Answer 2 · answered Apr 26 '16 at 13:09

A little bit late :) You can do it with properties:

<properties>
    <org.groupB.B.scope>compile</org.groupB.B.scope>
    <org.groupB.B.path></org.groupB.B.path>
</properties>

<dependency>
    <groupId>org.groupB</groupId>
    <artifactId>B</artifactId>
    <version>2.0</version>
    <scope>${org.groupB.B.scope}</scope>
    <systemPath>${org.groupB.B.path}</systemPath>
</dependency>

and then:

mvn package -Dorg.groupB.B.scope=system -Dorg.groupB.B.path=path/to/my-hacked-B.jar

Yang Bo · Accepted Answer · 2011-12-09T19:12:22.610

1

There is no way to resolve dependency from command line, but there is a way to let maven resolve dependency externally.

I created a temporal wrapper pom.xml which aggregates the two projects. It works, without install anything into local repository.

The only problem is that I am unable to use absolute path in <module/>.

See http://maven.apache.org/pom.html#Aggregation

edited Dec 09 '11 at 19:12

answered Dec 08 '11 at 02:29

Yang Bo

3,586
3
22
35

score 0 · Answer 4 · edited Jul 05 '22 at 23:36

You could mvn clean install your hacked version into your local maven repo, over the version you downloaded from the 'net. You'd need to make sure that project B's pom reflects the version you are depending on and not a snapshot version. (Or, to put it more generally: The version of project B that you mvn clean install must match the version you require in project A. Whether you edit A's pom or B's pom doesn't matter.)

How to resolve maven dependency explicitly from command line arguments?

4 Answers4