On 2017-11-25 14:35, rich...@xentu.com wrote:
I've written a few jersey webapps, and each has about 20 jar files
included as Maven dependencies.
The inclusion of those jars increases the size of the resulting wars
by a factor of over 100. Uploading a war via 'Tomcat Web Application
Manager'
One issue you might face in this configuration is if you have multiple versions
of the same library existing on the same path, let's say com.example v1.0 and
v2.0, and each is a dependency for one or more webapps. If a webapp depending
on 2.0 requires class com.example.X which is available in
I see by your paths that you are an MS person. Your solution is clever but has
the distribution problem that a war file may not be enough.
For Unix based folks (MAC, Linux), there is a much easier solution. Put your
common jars in some directory that you like (for me /opt/web_jars/acquired).
I've written a few jersey webapps, and each has about 20 jar files
included as Maven dependencies.
The inclusion of those jars increases the size of the resulting wars by
a factor of over 100. Uploading a war via 'Tomcat Web Application
Manager' takes several minutes, presumably due in part
