'Should I use fat JAR or not (wrapper on REST API)

I'm using JAVA to access a REST apis of a 3d party service. I'm trying to develop a wrapper to the REST api that will handle the authentication and authorization, and in addition, will parse requests/responses. (this project depends on - apache httpclient , jackson-core jars, Auth jar).

All the other projects should use the jar above, to access the APIs.

My question is, what is the better approach. To build the JAR above as a fat jar, with all the dependencies, or as a regular jar, and add in the consumers, the missing dependencies. (such jackson..)

Thanks!



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source