Closed mputnam-xima closed 4 years ago
Following...
Hi @mputnam-xima - Could you run the dependency tree and see if there are any conflicts on the jackson versions? @e-d - Are you getting the error too?
No conflicts in Jackson versions:
However, I haven't been able to rule out some sort of environmental/deployment problem on our end. I'm working on it, will update if I find anything
@diana-derose manually setting the Jackson version in my project to 2.9.10
(the same version used in the develop
branch) fixed it for me. However, I'm not sure if there's a problem with QuickBooks-V3-Java-SDK
or a something else going on with my project setup. Here are the lines I added in pom.xml
:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.fasterxml.jackson.module</groupId>
<artifactId>jackson-module-jaxb-annotations</artifactId>
<version>2.9.10</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.9.10</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-annotations</artifactId>
<version>2.9.10</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.jaxrs</groupId>
<artifactId>jackson-jaxrs-json-provider</artifactId>
<version>2.9.10</version>
</dependency>
</dependencies>
</dependencyManagement>
Thanks for letting me know. I'll do some more testing on my end and try to see if I can add all the dependency in the base pom and package it.
Hi @mputnam-xima - Could you run the dependency tree and see if there are any conflicts on the jackson versions? @e-d - Are you getting the error too?
@diana-derose I work with @mputnam-xima and wanted to be in-the-loop with what was happening. Thanks for looking into this.
I recently upgraded to release
6.0.4
. Refreshing the oath access token fails on this version, and downgrading to6.0.2
fixed the problem for us. Here is a related stacktrace, and please let me know if I can provide any more info to help you solve the issue, we need6.0.4
because it supportsBUSINESS_CHECKING
andBUSINESS_SAVINGS
accounts: