4 ms·

For large projects, fat JARs are slow to build. Unless you bundle JARs inside the JAR and use a special classloader, like Spring Boot... I don't use them at all

For large projects, fat JARs are slow to build. Unless you bundle JARs inside the JAR and use a special classloader, like Spring Boot... I don't use them at all because it's a pain. Plus you'd probably want to put your app code that changes in a different layer if you're doing docker images, as opposed to the other 90% of your app which is dependencies that rarely change

pjmlp 8y ago
That is what build servers are for.
- dionian 8y ago
  waiting on build servers is still waiting
  - pjmlp 8y ago
    Not if they are doing continuous builds on regular intervals. I guess waiting for building Docker images doesn't count then.
i386 8y ago
fat jars are just as expensive to create as war files. No matter which way you do this you’re going to be copying a lot of files around.