How to Upload Jar to Nexus Repository

A common issue in Maven development is the incorporation of 3rd-party JARs into a repository. If you are working with a proprietary database similar Oracle, or if you have a vendor that is supplying you with some proprietary 3rd-party JAR that needs to be incorporated into your build, what do you do? How do you get this JAR into a Maven repository that your build can admission? This is a common question when people want to start publishing artifacts in a custom repository, and most Maven users might not be enlightened that repository managers like Sonatype Nexus provide an easy way to deploy these floating, i-off JAR files as well as a style to deploy artifacts from your ain build. The following diagram illustrates the apply-case which attracts nearly initial Nexus users: proxying of remote repositories.

While proxying remote repositories and maintaining a local cache is certainly important, it isn't the most transformational feature of a good repository. You really start to realize the benefits of a repository manager one time you get-go deploying artifacts to it. In one case users start to utilize Nexus hosted repositories they start to see Nexus as a cardinal collaboration point for sharing artifacts throughout an organization. No more manus-crafted POMs distributed in an email for developers to install in a local repository. If the organization uses a JDBC driver for Oracle, which is not bachelor on a public repository similar Central, that artifact can be deployed on your instance of Nexus and made bachelor in the hosted 3rd-political party repository which comes preconfigured with every Nexus instance.

Dorsum to the original question: someone just handed you lot a JAR file that is essential to your projection's build; how do you become this JAR into a Maven repository?

Erstwhile Respond: Handmade POMs and Repositories

Years ago, when the Maven repository was new, and before people had started to work on repository managers, you lot commonly just created a filesystem somewhere in your organization with the appropriate directory construction and pointed everyone'south build to information technology. Maybe you'd go equally far as configuring a spider web server like Apache HTTPd to serve your ad hoc, handcrafted repository. All you needed was a uncomplicated POM file with basic elements: projection, groupId, artifactId, version, packaging, proper noun. Other than that, checksums were optional. (As long as the filesystem looked like the filesystem on http://repo1.maven.org/maven2 or ${groupId}/${artifactId}/${version}/${artifactId}-${version}.${packaging}, Maven should be able to read information technology.)

If y'all were really unlucky, perchance the group of developers you worked with but kept on passing around a Nil archive that people would download and uncompress in ~/.m2/repository. "Oh, you don't take the Oracle JDBC driver in your local Maven repository.... Here, read this Wiki page, information technology should only have you 10-15 minutes to re-create the right files to your local repo..." I've seen this manner of collaboration every bit recently equally final year for things like the Oracle JDBC driver, and I'thou certain a few of you reading this are nevertheless working at a large organisation notwithstanding to be convinced of the need for a repository manager. While handcrafting POMs and passing around archives for local repositories might be working for some people, there is a much easier way to load the 1-off artifact into a repository...

New Reply: Upload Artifacts to Sonatype Nexus Repository Manager

There's a much easier solution than handcrafting a POM for a 3rd-political party JAR. Sonatype's Nexus provides a very easy way to upload artifacts to a hosted third-party repository. You lot can upload using the Maven Deploy Plugin or y'all tin can upload via the web interface. Because information technology is so straightforward, I'm going to include the steps for downloading, installing, starting Nexus, and then uploading a 3rd-party JAR. Nexus has very low resource requirements, and it is something y'all tin can run on an existing workgroup collaboration auto or locally. When you upload a 3rd-party JAR to your own Nexus case, it will immediately be integrated with Nexus search capabilities and be available to your organization's builds. In terms of the time required to upload and configure a POM for a 3rd-political party JAR, zilch beats the 2 minutes, start to end, it will accept you to download and configure a basic case of Nexus.

If yous want to download Nexus and deploy a 3rd-party JAR to a Nexus hosted repository, here are the steps required:

1. Download Nexus: http://nexus.sonatype.org/downloads/nexus-ane.1.1-parcel.nix (Information technology is open source, free)
2. Unpack information technology in a directory (anywhere, it doesn't thing where)
3. Start Nexus with ./bin/jsw/macosx-universal-32/nexus start (different OS directory depending on platform)
4. Go to "http://localhost:8081/nexus"
5. Login as user: "admin" password: "admin123"
6. Click on "Scan Repositories," and you'll encounter a list of repositories. Yous will want to right click on the "tertiary Party" repository and cull "Upload Artifact."
7. You will then meet an "Upload Artifact" course. Choose the JAR to upload, then populate the group id, antiquity id, version, and other fields.

It will end upward in a Maven Repository with the appropriate structure + a checksum. Nexus will update the Nexus Alphabetize which will make it bachelor in the search results. You tin then use the filesystem that Nexus created, or you can just configure your local Nexus case as a repository in Maven. To configure your newly installed instance of Nexus as a mirror for Maven, put the following in your ~/.m2/settings.xml file:

<stiff><span fashion="color: blue">?xml version="1.0"?</span></potent> <stiff><span style="color: blue">settings</span></strong>   ...   <stiff><span way="color: blue">mirrors</bridge></stiff>     <potent><span style="color: bluish">mirror</span></strong>       <potent><span mode="color: blue">id</span></stiff><Nexus><stiff><span style="color: blue">/id</span></strong>       <strong><span style="color: bluish">name</span></stiff>Nexus Public Mirror<strong><span manner="color: blue">/name</span></strong>       <strong><bridge style="color: blue">url</bridge></strong>http://localhost:8081/nexus/content/groups/public<strong><span style="color: blue">/url</span></strong>       <potent><bridge mode="colour: blueish">mirrorOf</span></strong>fundamental<stiff><span style="colour: blue">/mirrorOf</span></strong>     <strong><span style="colour: blue">/mirror</span></strong>   <potent><span style="color: blue">/mirrors</span></strong>   ... <strong><span way="colour: bluish">/settings</bridge></strong>

Tags: Nexus Repo Reel, Everything Open Source, Maven

henningthased.blogspot.com

Source: https://blog.sonatype.com/2008/11/adding-a-jar-to-a-maven-repository-with-sonatype-nexus/#:~:text=Go%20to%20%22http%3A%2F%2Flocalhost,and%20choose%20%22Upload%20Artifact.%22

Share this post