title: Commons Jars, pack or not?
body: <p>the closest I found was this topic: <a href="https://stackoverflow.com/questions/6158148/using-maven-how-to-properly-deploy-war-depending-on-j2ee-jpa-jar">Using Maven, how to properly deploy WAR depending on J2EE/JPA JAR?</a>, but it doesn't answer the question.</p>
  
  <p>Nowadays I am working in a project with 5 web components and they all use a "core" jar, with the entities, enum. The common stuff.</p>
  
  <p>Currently we pack the "core" jar inside of each component war. The downside is that you need to generate all components when the core has changed. In order to avoid Serialization and  Marshalling problems. </p>
  
  <p>One solution  I thought is to generate the war solo and put all it's dependencies into a lib folder. The downside of this is forget to add a certain dependecy.</p>
  
  <p>Do you know any other way to deal with this situation?</p>