On Wed, Oct 8, 2008 at 11:33 AM, Rick <[EMAIL PROTECTED]> wrote: > In a typical JEE project I have a parent module that my children all > inherit from. My modules look like: > > parent > ear > ejb > web > jar > > My debate is how to best put this into version control? Do most of you > commit the parent directory that holds all the submodules as 'one > project' or do some of you like to commit each module separately? I'm > leaning towards just checking in the whole parent directory as one > project, since the modules are all so closely related. Although the > jar file (Which is mostly util stuff can really be stand alone I > suppose and in theory the ejb module could be used by another web > project, but that's extremely unlikely. ) >
Depends a lot on the specifics. For the most part, I'll commit this kind of work as a single project. Where I feel like there are truly re-usable elements (things that I will reuse, not "might reuse"), I'll tend to separate those and only those into their own top-level projects. In essence, if a group of modules are likely to change together and be released and deployed together, I'll treat them as a single project with modules. When one or more of those starts to develop its own lifecycle, I'll start splitting them off into their own projects. Make sense? - Geoffery -- Geoffrey Wiseman
