In this case, both Maven and Nexus were chosen because they were currently being used by our team. This way, we can have access to multiple external libraries and different versions of them. When talking about “artifacts”, we mean external libraries like, for example, JARs files for Java libraries and packages for Node. Nexus is a repository manager that stores “artifacts”, which allows you to proxy collect and manage your dependencies, making it easy to distribute your software. Maven dynamically downloads Java libraries and Maven plug-ins by accessing one or more repositories such as the Maven 2 Central Repository, and stores them in a local cache. It uses a XML file describing the software project being built, its dependencies on other external modules and components, the build order, directories, and required plug-ins. Maven is a build automation tool used primarily for Java projects that addresses how software is built and its dependencies. In this article, we will be showing how to deploy Java artifacts using both technologies, but first, let’s have a brief explanation of what they are. Together they help build and manage Java dependencies in a simple and reliable way. This is where Maven and Nexus come into play.

Therefore, having multiple versions without a minimum management can be quite dangerous. This process generates files and these files generally are related to a version. Different forms of management exist and they were created based on multiple projects’ natures and technologies.įor some languages, the source code needs to be compiled first in order for it to be executed by the machine.

Deploying Java artifacts on a Nexus Repository with MavenĪs a software project grows, the number of dependencies increases, requiring the need of managing them in a scalable manner.

Nexus artifact repository installation