Maven - External Dependencies

As you know, Maven does the dependency management using the concept of Repositories. But what happens if dependency is not available in any of remote repositories and central repository? Maven provides answer for such scenario using concept of External Dependency.

For example, let us do the following changes to the project created in ‘Creating Java Project’ chapter.

  • Add lib folder to the src folder.

  • Copy any jar into the lib folder. We've used ldapjdk.jar, which is a helper library for LDAP operations.

Now our project structure should look like the following −

external repository project structure

Here you are having your own library, specific to the project, which is an usual case and it contains jars, which may not be available in any repository for maven to download from. If your code is using this library with Maven, then Maven build will fail as it cannot download or refer to this library during compilation phase.

To handle the situation, let's add this external dependency to maven pom.xml using the following way.

<project xmlns = "" 
   xmlns:xsi = ""




Look at the second dependency element under dependencies in the above example, which clears the following key concepts about External Dependency.

  • External dependencies (library jar location) can be configured in pom.xml in same way as other dependencies.

  • Specify groupId same as the name of the library.

  • Specify artifactId same as the name of the library.

  • Specify scope as system.

  • Specify system path relative to the project location.

Hope now you are clear about external dependencies and you will be able to specify external dependencies in your Maven project.