Too many Jar dependencies while using ES Transport client


I have been using ES Transport client in our product to fetch data from ES Server.

When I use below maven dependency and build the project:


There are more than 30 jars that are getting shipped along with this jar.

Same is the case if I use ES-Spark connector where I see more than 100 jars being shipped.

What can be done for this one ? because shipping these many jars every time for new deployment is not a good practice.

May be this can help:

Thanks but I need to solve issue of shipping too many jars along with my maven build. What can be done to ship only client jar ?

Shade your project. It will produce one single jar containing all classes.
You don't need to do any relocation. Just shade.

My 2 cents

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.