What you want can be achieved by having one big aggregator that contains all your modules and your ears, and use the reactor feature.
By typing mvn -pl my-project:app -am, where my-project:app is the groupId of your ear, you will actually build the ear and all its transitive dependencies accross your whole reactor. I would also add that in an environment where you have continuous integration, with snapshots deployed regularly on a corporate repository, the need to build everything from scratch will vanish as you will need to build only what you changed and its downstream dependencies (-amd is very useful for that) Vincent 2010/11/9 KARR, DAVID (ATTSI) <[email protected]> > > I currently work on a large enterprise app built with Ant. The app is > divided into several projects divided into functional areas. In order > to build the entire EAR, all of the projects have to be built, even if > you're only working on a single one of those projects. > > I'm examining how we could make this work better if we were using Maven. > > I guess a straightforward implementation of this would have a main > project POM that specifies all the subprojects as submodules, and also > their artifacts as dependencies. > > It almost seems to me that what I need is the ability to have the main > POM be somewhat "dynamic", such that if I'm only working on a single one > of those subprojects, but I need to assemble the EAR containing all of > the artifacts, then the projects that I don't have checked out would get > their submodule entry temporarily deleted, and I would get their > artifacts from the intranet repo. > > I would be using m2eclipse. > > Does any of this make sense? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
