# Build failure with the 0.19.10 version **URL:** \ **Category:** Elasticsearch\ **Created:** [October 2, 2012, 8:41pm UTC](https://discuss.elastic.co/t/build-failure-with-the-0-19-10-version/9217 "2012-10-02T20:41:47Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [October 2, 2012, 8:41pm UTC](https://discuss.elastic.co/t/build-failure-with-the-0-19-10-version/9217/1 "2012-10-02T20:41:47Z")
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): - - But the path does exist: $ ls ../third\_party/elasticsearch-0.19.10/lib ../third\_party/elasticsearch-0.19.4/lib ../third\_party/elasticsearch-0.19.10/lib: elasticsearch-0.19.10.jar log4j-1.2.17.jar lucene-core-3.6.1.jar lucene-memory-3.6.1.jar sigar jna-3.3.0.jar lucene-analyzers-3.6.1.jar lucene-highlighter-3.6.1.jar lucene-queries-3.6.1.jar snappy-java-1.0.4.1.jar ../third\_party/elasticsearch-0.19.4/lib: elasticsearch-0.19.4.jar log4j-1.2.16.jar lucene-core-3.6.0.jar lucene-memory-3.6.0.jar sigar jna-3.3.0.jar lucene-analyzers-3.6.0.jar lucene-highlighter-3.6.0.jar lucene-queries-3.6.0.jar 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. Thoughts? Thanks in advance! -- ---
**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\ **Post date:** [October 2, 2012, 9:04pm UTC](https://discuss.elastic.co/t/build-failure-with-the-0-19-10-version/9217/2 "2012-10-02T21:04:17Z")
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. Martijn On 2 October 2012 22:41, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com) 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): > > - > > - > > But the path does exist: > > $ ls ../third\_party/elasticsearch-0.19.10/lib > ../third\_party/elasticsearch-0.19.4/lib > ../third\_party/elasticsearch-0.19.10/lib: > elasticsearch-0.19.10.jar log4j-1.2.17.jar lucene-core-3.6.1.jar > lucene-memory-3.6.1.jar sigar > jna-3.3.0.jar lucene-analyzers-3.6.1.jar > lucene-highlighter-3.6.1.jar lucene-queries-3.6.1.jar > snappy-java-1.0.4.1.jar > > ../third\_party/elasticsearch-0.19.4/lib: > elasticsearch-0.19.4.jar log4j-1.2.16.jar lucene-core-3.6.0.jar > lucene-memory-3.6.0.jar sigar > jna-3.3.0.jar lucene-analyzers-3.6.0.jar > lucene-highlighter-3.6.0.jar lucene-queries-3.6.0.jar > > 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. > > Thoughts? > > Thanks in advance! > > -- -- Met vriendelijke groet, Martijn van Groningen -- ---
**Author:** ![brian\_yoder](https://avatars.discourse-cdn.com/v4/letter/b/f1d935/32.png) [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)\ **Post date:** [October 2, 2012, 9:55pm UTC](https://discuss.elastic.co/t/build-failure-with-the-0-19-10-version/9217/3 "2012-10-02T21:55:10Z")
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): > > - > > - > > But the path does exist: > > $ ls ../third\_party/elasticsearch-0.19.10/lib > ../third\_party/elasticsearch-0.19.4/lib > ../third\_party/elasticsearch-0.19.10/lib: > elasticsearch-0.19.10.jar log4j-1.2.17.jar > lucene-core-3.6.1.jar lucene-memory-3.6.1.jar sigar > jna-3.3.0.jar lucene-analyzers-3.6.1.jar > lucene-highlighter-3.6.1.jar lucene-queries-3.6.1.jar > snappy-java-1.0.4.1.jar > > ../third\_party/elasticsearch-0.19.4/lib: > elasticsearch-0.19.4.jar log4j-1.2.16.jar > lucene-core-3.6.0.jar lucene-memory-3.6.0.jar sigar > jna-3.3.0.jar lucene-analyzers-3.6.0.jar > lucene-highlighter-3.6.0.jar lucene-queries-3.6.0.jar > > 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. > > Thoughts? > > Thanks in advance! -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:10am UTC](https://discuss.elastic.co/t/build-failure-with-the-0-19-10-version/9217/4 "2017-07-06T03:10:27Z")
Closed on July 6, 2017, 3:10am UTC