-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naming clash with Joda convert classes #10290
Comments
Same issue here. Cannot create our own packaged application, because elasticsearch.jar contains the above-mentioned joda-classes. |
here's how to reproduce this issue:
Assembly fails with ES 1.5.0. However, if you edit |
Very annoying bug effectively preventing us from creating fat jar in our project. Looking back to original issue #4660 that introduced monkey-patched files from joda-convert into ES I can only sigh at how developers sometimes do things purely wrong and forget about it until it blows up someday. I can't even use usual sbt/sbt-assembly stuff to exclude these files during build. That's unacceptable. |
Yup, I'm also unable to build a package because of this. |
can you guys use the shaded jar? <groupId>org.elasticsearch.distribution.shaded</groupId>
<artifactId>elasticsearch</artifactId> |
Oh, I'm not familiar with that. Do you know how I would use that in sbt? |
I don't know sbt but how do you use elasticsearch? |
|
So the shaded package is only available as 2.x? I'm not sure if that will work. Also, I'm using https://github.com/sksamuel/elastic4s, which maybe has a dependency on the non-shaded elasticsearch, so even when I try the shaded package I still get errors about conflicting versions of elasticsearch. |
yeah the 1.x dev branch is closed we are mainly focusing on 2.x now |
2.0.0 isn't even out of beta. Please fix this issue. It's super annoying. Just do a point release! (1.7.2) |
Closed by #13358 |
elasticsearch.jar (v1.5.0) re-packages Joda convert classes:
this will create a naming clash in projects that use Joda convert.
The text was updated successfully, but these errors were encountered: