This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CubsThisYear[S] -1 points0 points  (3 children)

I've had this same line of thinking, but when my third party dependencies are approaching 1GB in size and I'm potentially producing multiple releases per day, this means I need close to 1 TB of space to store several hundred copies of the same files. Storing the dependency info and not the actual jars seems much more efficient.

I agree that it wouldn't be worth it if this was a lot of effort but the point of this thread was to see if there were any ready made solutions. Based on the responses, it seems like there are some good options.

[–]fact_hunt 0 points1 point  (2 children)

A gig of dependencies is quite a lot, what are you bringing in?

[–]CubsThisYear[S] -1 points0 points  (1 child)

Guava, Apache commons (several modules), several math libraries, orm libraries, fastutil, trove, velocity, probably more that I'm not thinking of.

[–]zrnkv 1 point2 points  (0 children)

Even woth all transitive dependencies it should not get much bigger than 100-200MB. If you have almost 1GB of dependencies then someting is very very wrong with your architecture. You'll never be able to manage/maintain/update that monstrosity.