plaid-java: Readme references 2.0.0 but I don't see any version past 0.3.2 in the Maven link

Is this just pending a release or not done yet? Sorry not really an issue but I couldn’t think of a better way to reach out about the status.

I see the <version>2.0</version> but the link above that part only shows up to v0.3.2

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 7
Comments: 20 (5 by maintainers)

Most upvoted comments

2.1.0 has been published to maven:

<dependency>
  <groupId>com.plaid</groupId>
  <artifactId>plaid-java</artifactId>
  <version>2.1</version>
</dependency>

https://oss.sonatype.org/service/local/repositories/releases/content/com/plaid/plaid-java/2.1/plaid-java-2.1.jar

It should sync to the central Maven repository shortly. Thank you again to everyone for their patience. Please continue to share problems or issues here with the release.

michaelckelly on May 3, 2017

@dwoodworth91 - Thank you for supplying the workaround in the interim.

I hope that we can resolve the permissions issues once and for all this week – the POM file should be updated to reflect the appropriate repository and package names (apologies for not having those properly up-to-date).

A few unit tests that were failing have also been fixed (mainly due to introducing support for the Income product).

The 2.0.0 / 2.1.0 jar is successfully building with tests passing locally but a permissions issue is preventing the release to be pushed to the Sonatype repository. Once that’s resolved, we should be unblocked for the release.

Thank you to everyone for the patience and help here and please follow up here with any additional questions.

michaelckelly on Apr 18, 2017

Thanks for the ping here @all and apologies for the lack of reply. We’re sorting out permissions issue to get the release out. The 2.0.0 release is merged in this repository and ready-to-go (the integration tests provide a good jumping off point).

We’re working on an alternative name to publish the jar to resolve this ASAP.

michaelckelly on Apr 11, 2017

Thanks for the detailed procedure to get it working @dwoodworth91

ufdeveloper on Apr 14, 2017

If it helps anybody, I was able to get going by checking the project out with git, then building it with Maven and dropping it into a configured local Maven repo - mimicking the directory and naming scheme that you can ape by looking at Maven Central.

Rename JAR to “plaid-java-2.0.jar” It’ll be under [project-root] -> target, and named “plaid-java-apiv2-2.0.jar”
rename project POM to “plaid-java-2.0.pom”
Drop both files into: [repo-root] -> com -> plaid -> plaid-java -> 2.0

It is already set up to build a JAR, so if you know Maven, you should be golden. If you don’t want to configure a local Maven repo in your main project, you could probably also just do what is described above in your local Maven cache.

dwoodworth91 on Apr 13, 2017

@mihahribar @OscarGodson @dwoodworth91 FWIW currently I have manually included the version in master to my scala project until there is resolution on this. I had to add the retrofit2 and okhttp3 dependencies to my own project and then it worked. Janky for sure, but it’s working and reaching plaid 👍

dadambickford on Apr 11, 2017