george-hawkins-work
commented
8 years ago For reference Quandl4J works fine if we pull it in like this:
<dependency>
<groupId>com.jimmoores</groupId>
<artifactId>quandl</artifactId>
<version>1.3.0</version>
<exclusions>
<exclusion>
<groupId>com.opengamma.external.json</groupId>
<artifactId>json</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20160810</version>
</dependency>I understand the reasons you outline in #11 for not including org.json:json - the clause you refer to is indeed childish and stupid (quite apart from any legal aspects).
Maybe it's time to consider Jackson. We use it for all our JSON related work (as do Spring and pretty much everyone else). E.g. parsing arbitrary JSON into a Map is as easy as:
String jsonString = ...
ObjectMapper mapper = new ObjectMapper();
Map<String, ?> data = mapper.readValue(jsonString, new TypeReference<Map<String, ?>>() { });
jimmoores
We have been using quandl4j for a while without problem but a new employee had issues. The reason was we all have
com.opengamma.external.jsoncached in our local.m2repositories but it seems maven.opengamma.com is no longer publishing old artifacts like this.OpenGamma now seems to have a space on bintray and they also seem to be publishing their main products, like Strata, to Maven Central (e.g. see the Strata README).
I just tried building quandl4j locally but without much luck due its dependence on maven.opengamma.com. I suggest clearing out
~/.m2/repository/com/opengammaand seeing if you have the same issues (if you have something like Sonatype Nexus proxying remote repos for you then you'll obviously have to clear out things there too).