If you don’t have Maven repository server like Archiva or Nexus, you may need to include those libs which are not public on the internet in your Maven project and specifiy the dependency scope as system in the pom.xml. The following example includes the eureka-0.0.1.jar which is located in the folder called external on project root.
...
<dependency>
<groupId>ykyuen.info</groupId>
<artifactId>eureka</artifactId>
<version>0.0.1</version>
<scope>system</scope>
<systemPath>${project.basedir}/external/eureka-0.0.1.jar</systemPath>
</dependency>
...
A few months ago i wrote a blog post about how to package the project jar file with all dependencies.
Maven – Package the jar file with dependencies
Continue reading Maven – Include system scope dependency in maven-assembly-plugin →
It is possible to add other Maven repositories which is specified explicitly in the pom.xml using the <repositories> node. But if you have a Maven Repository Manager like Archiva, you should configure those remote Maven repostories in Archiva instead of adding them in the pom.xml
Continue reading Maven – Add New Remote Maven Repository in Archiva →
You have to specific the plugin dependency in the pom.xml if u want to use the installer task of AntInstaller in Maven.
Continue reading Maven – Using AntInstaller in Maven →
So we know how to install the Archiva.
Maven – Archiva Installation
The next task is to configure the Maven such that it will download the dependencies through the Archiva.
Continue reading Maven – Setup mirror to Archiva Repository Manager →
Archiva is a repository manager which is necessary for development in Maven for 2 purposes.
1. Add your own dependencies to the repository in Archiva in case if they are not found in the public Maven repository like http://repo1.maven.org/maven2/
Continue reading Maven – Archiva Installation →
Dream BIG and go for it =)