Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If we are building a large library of java classes, what determines when it is best to split them into separate jar files?
My understanding is that having one large jar file should not significantly affect the JVM performance. However, there is some development cost if an entire suite of lengthy tests are run when changes or additions are made to the jar. Is there a cost or benefit when using large jar files with maven and archiva?
What strategy do people use in practice?
Take into account change management aspects only, the rest is negligible. Jar file is something that determines minimum easily-releasable unit.