Part of your problem could/(should?) be resolved with parent poms. A good read is the sonatype maven book ( http://www.sonatype.com/products/maven/documentation/book-defguide)
Patrick On 10-03-02 02:18 PM, user09772 wrote: > > > dahoffer wrote: > >> Without knowing details all I can give are general suggestions... >> >> - Things you want to version/branch as a unit go in the same project >> (may have several modules). >> - Common things that are used in more than one project go in a >> separate project (may have several modules) and are depended on as >> needed. >> >> -Dave >> >> >> >> > Thanks for the response. > > Right. so all the projects i mentioned would need to be versioning (the > commands will change that the services use, the services will change that > the rest projects use etc.). That is at a high level point of view right. > I'm probably thinking more on how to use Maven modules to provide separation > between each of the components. > > The main thing i would like to accomplish is have the ability to switch out > any of the projects (modules?) with another one and build the system using > those new modules. >
