The main inconvenient is the fact that you need to install a repository manager 2. The main advantage if this approach is that once the JAR downloaded and installed in the repository manager it will be available for all the users and future projects Once the JAR is installed in the repository it will be available to anyone that uses the repository as long as your settings.xml file or pom.xml file are properly configured. There is a nice comparison matrix over here so you can make and educated choiceĪnyhow if you or your company have a repository manager you can easily install the required JAR on your repository. I never used Archiva but I really like Nexus.
I will not go into the details of the different repository managers but there are mainly 3 This is where you can store your companies jars and wars and some other jar not available in the public repositories There are a few maven repository managers out there which allow mainly to mirror distant maven repositories such as maven central, by storing the remote jars locally and making them available inside the company Using Maven repository repository manager When developing a team project and that you are required to use a jar of this type you have mainly 3 options : 1.
#Maven install with 3rd party jar example driver
the oracle jdbc driver that is not available for copyright reasons) When using some third party dependencies in a maven project you realize that sometimes some of jars are not available in any of the public maven repositories available (e.g.
0 kommentar(er)
