Managing the ELS repository
This page provides instructions for upgrading to newer TuxCare package versions, accessing source code for ELS-patched libraries, managing the TuxCare NuGet source for .NET projects, and consuming the Java repository through your own repository manager.
How to Upgrade to a Newer Version
If you have already installed a package with a tuxcare.1 suffix and want to upgrade to a newer release (for example, tuxcare.3), update the version string in your Maven or Gradle build file with the version listed in your TuxCare Nexus account.
Source code
Source code is available for TuxCare-patched Java libraries. Source JARs follow the standard Maven naming convention with a -sources classifier and are published to the Nexus repository.
If a source JAR is not available for a specific package, please contact sales@tuxcare.com.
Consuming ELS through your own repository manager
Instead of pointing Maven or Gradle directly at https://nexus.repo.tuxcare.com/repository/els_java/, you can proxy the TuxCare Java repository through your own repository manager. This is optional and intended for organizations that already run one — otherwise ELS connects directly, as described in the setup steps on each library's page.
The steps below use the Java repository (els_java) as an example, but the same approach applies to any ELS ecosystem — only the repository format, remote URL, and authentication differ.
Create the proxy repository
In your repository manager, create a Maven-format repository that proxies an external URL. Depending on the product, this type is called a proxy or remote repository.
Point it at the TuxCare repository
Set the remote URL to
https://nexus.repo.tuxcare.com/repository/els_java/and supply your ELS credentials via HTTP Basic authentication (your TuxCare Nexus username and password).Repoint your build tools
Configure Maven or Gradle to resolve against your own repository manager instead of
nexus.repo.tuxcare.com. Artifacts are fetched from TuxCare and cached on demand the first time they are requested.
A proxy only caches and serves the artifacts that have actually been requested through it, so browsing your proxy will not show the full TuxCare catalog. This is expected behavior, not a permissions problem.
To see the full list of available artifacts and versions, sign in to the TuxCare Nexus with your ELS credentials and browse the els_java repository directly. For automation or scripted checks, you can query the Nexus REST API components or search endpoints instead (for example, /service/rest/v1/components?repository=els_java), which return the full catalog regardless of what your proxy has cached, paginated via a continuationToken.
