I'm a bit confused on the best practice for working with maven projects within a version control system.
For example assuming we have a company repository setup and we are working on EJB project (ear) with your standard components (war and a few jars). Do people typically set up a FooBar ear project and check that into version control including the parent pom.xml and sub modules as part of a FooBar project? Or is better to just check in the parent ear pom as part of a FooBar project that has nothing in it but the parent pom.xml, and then checkin all the modules separately into version control? Typically (using ant) I'd create an ear project and include the modules that are 'tightly tied' to this project, but move out other projects that can obviously be shared easily amongst other projects. I assume the seem logic would apply to maven2 projects? Just want to make sure I'm not missing a best practice before I get too deep down the maven2 path here. Thanks, -- Rick
