I've heard that there are issues with other jar files in which embedded
classpath information adversely affects the build.
By the way, the same error also occurs with version 19.9. Only version 19.4
builds with my application, even though I can see the Jackson class within
each of the elasticsearch JAR files.
The Response class doesn't look like an ES class what is using the
'org.elasticsearch.common.jackson' package in your code?
From the ES pom.xml I see that jackson (com.fasterxml.jackson) is
shaded into the org.elasticsearch.common.jackson package.
I've heard that there are issues with other jar files in which embedded
classpath information adversely affects the build.
By the way, the same error also occurs with version 19.9. Only version 19.4
builds with my application, even though I can see the Jackson class within
each of the elasticsearch JAR files.
My fault. I had wanted to create the smallest possible application and use
only the classes provided in the Elasticsearch distribution. I had not
noticed that the Jackson stream parser had been moved slighlty.
All is building and working fine now.
On Tuesday, October 2, 2012 4:41:47 PM UTC-4, InquiringMind wrote:
The code built on 19.4 OK. Trying to migrate to most recent version 19.10
Snippet of ant build failure:
[javac] .../database/Response.java:10: package
org.elasticsearch.common.jackson does not exist
But the only change in build.xml is (- is working original version; + is
new broken version):
I've heard that there are issues with other jar files in which embedded
classpath information adversely affects the build.
By the way, the same error also occurs with version 19.9. Only version
19.4 builds with my application, even though I can see the Jackson class
within each of the elasticsearch JAR files.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.