Home/ Questions/Q 5928965
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T14:21:31+00:00

I am using a local repository as described in Maven: add a dependency to

  • 0

I am using a local repository as described in Maven: add a dependency to a jar by relative path.

The repository-url is defined in the topmost pom.xml as

<url>file:${basedir}/../3rdParty/maven-repository</url>

Also, the topmost pom.xml defines 2 modules

<modules>
    <module>sub1</module>
    <module>sub2</module>
</modules>

The problem is, that if a module (say sub1) defines a dependency that should be downloaded from the repository, and maven is called from the topmost directory, the ${basedir} is not set to this directory, but to sub1, resulting in a wrong repository-URL.

So, say the project with the topmost pom.xml resides in 

/Development/myproject/pom.xml

And the repository is in 

/Development/3rdParty/maven-repository

Then the repository URL should be set to 

/Development/myproject/../3rdParty/maven-repository

but it turns out it is set to 

/Development/myproject/sub1/../3rdParty/maven-repository

which of course does not exist.

Any idea why that is the case?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Although it is annoying in your case, this is well-known and intentional. A maven project should know about its execution directory only, no matter in what context it is executed.

    I asked almost the same question: Maven variable for reactor root earlier, and the only answer that made sense was to use ${user.dir}, although it’s hacky and will not work if you build from a module directory.

    (There is also this very verbose solution: Maven2 property that indicates the parent directory)

    • 0