0

I want to use this jar in a Maven project.

https://github.com/downloads/2checkout/2checkout-java/twocheckout-java-latest.jar

I know that the proper way is to add this jar into my local repository but I can't do this into every development machine. Is there any Maven plugin that can download this jar file and add it into my project?

Wim Deblauwe
  • 25,113
  • 20
  • 133
  • 211
Peter Penzov
  • 1,126
  • 134
  • 430
  • 808

4 Answers4

1

There are only 3 options in a case like this:

  1. Convince the people of the project to put their releases in Maven Central. See Guide to uploading artifacts to the Central Repository for more information on that.
  2. Install a Maven proxy (e.g. Sonatype Nexus, see http://www.sonatype.org/nexus/) and upload the artifact manually. Each developer on the project can point to that proxy and will get the artifact.
  3. Use the maven-install plugin to have each developer install the jar on his own local repository.
Wim Deblauwe
  • 25,113
  • 20
  • 133
  • 211
0

You can add below dependency into your pom.xml

<dependency>
  <groupId>com.twocheckout</groupId>
  <artifactId>twocheckout-java</artifactId>
  <version>0.1.0</version>
</dependency>
Adil Shaikh
  • 44,509
  • 17
  • 89
  • 111
  • I already thied this but looks like the jar file into the repository is corrupted. The size is 2,1 KB – Peter Penzov Aug 23 '16 at 14:19
  • This only works if the artifact is available in Maven Central, but it is not: http://search.maven.org/#search%7Cga%7C1%7Ctwocheckout-java – Wim Deblauwe Aug 23 '16 at 14:29
0

The usual way to deal with this sort of situation is to use a shared repository such as nexus or artifactory. You configure the nexus repository to serve the locally-uploaded artifacts and you configure your pom to point to your nexus repository as one of the repositories where the artifact may be found. Then, you install the problematic artifact to the nexus repository (rather than every developer's local repository).

If desired, you can also configure your nexus to be a proxy for Maven Central (and all other repositories that you use) and have your pom configured to look only there. This results in a cache of all the artifacts that you use being held locally, which can improve performance and availability for your team (if they are co-located). This can be especially important if you have a dependency on a SNAPSHOT version that is stored in a remote repository.

Rob
  • 6,247
  • 2
  • 25
  • 33
0

The best way is to have a proxy repository installed in your corporate LAN and deploy these kind of jars in to "hosted" repositories. Then editing your settings.xml to have this as your repository.

The choice of local proxy varies from using a NAS based shared drive to using repository managers like 'Nexus' or 'Artefactory'. This way you can easily distribute the artefacts across developers and all other users.

skn
  • 21
  • 1