This is by far the easiest and most reliable option available. That leaves the third option – adding the artifact in source control and using a maven plugin – in this case, the maven-install-plugin to install it locally before the build process needs it. In addition, the library may not be Maven enabled at all, which makes the process that much more difficult, so it's not a realistic solution to being able to use the artifact NOW. Getting the artifact uploaded into a public repository or in Maven central directly is also a good solution, but usually a lengthy one. The following listing contains the update site for the Neon release and an update site maintained by the m2e project.

If it is missing in your installation, you can install it via the main update of your release via Help > Install New Software. If this scenario – hosting custom artifacts – is a common one however, a repository manager makes a lot of sense. Install the Maven support for Eclipse (m2e) Most Eclipse downloads include the Maven tooling already. Provisioning an instance to run Nexus, setting up Nexus itself, configuring and maintaining it may be overkill for such a simple problem as using a single jar. Nexus is of course the more mature solution, but it's also the more complex. install the artifact locally using a maven plugin.try to get the artifact uploaded into one of more reputable public repositories.

bite the bullet and install a full fledged repository management solution such as Nexus.When that happens, there are a few choices: However there will always be an artifact that is either not hosted anywhere, or the repository where it is hosted is risky to depend on, as it may not be up when you need it. Maven is a very versatile tool and its available public repositories are second to none.

How to install maven jar in eclipse