Revision history [back]

in such cases I use a system scoped dependency, even though it's deprecated it often helps during local development. I usually create a folder /lib-ext below my project. And place local jars there, then I add a system dependency like this:

<dependency>
    <groupId>some.group</groupId>
    <artifactId>any-artifact</artifactId>
    <version>0.0.0</version>
    <systemPath>${project.basedir}/lib-ext/any.jar</systemPath>
    <scope>system</scope>
</dependency>

in such cases I use a system scoped dependency, even though it's deprecated it often helps during local development. I usually create a folder /lib-ext below my project. And place local jars there, then I add a system dependency like this:

<dependency>
    <groupId>some.group</groupId>
    <artifactId>any-artifact</artifactId>
    <version>0.0.0</version>
    <systemPath>${project.basedir}/lib-ext/any.jar</systemPath>
    <scope>system</scope>
</dependency>

in such cases I use a system scoped dependency, even though it's deprecated deprecated it often helps during local development. I usually create a folder /lib-ext below my project. And place local jars there, then I add a system dependency like this:

<dependency>
    <groupId>some.group</groupId>
    <artifactId>any-artifact</artifactId>
    <version>0.0.0</version>
    <systemPath>${project.basedir}/lib-ext/any.jar</systemPath>
    <scope>system</scope>
</dependency>

An not deprecated alternative is to place the jar into a local repository:

https://stackoverflow.com/questions/3765903/how-to-include-local-jar-files-in-maven-project/19226672#19226672