Yeah, I've used both approaches, overlays and profiles. We generally use profiles because they are faster, especially if you don't need to always create all container variants; if you need them all, always, then overlays might be just as good. (Right, overlays work with wars not sure about ears.)
-Dave On Tue, Jan 19, 2010 at 9:47 AM, Manfred Moser <[email protected]> wrote: > On Tue, 19 Jan 2010 11:29:54 -0500, David.A.Williams wrote > > We have a project that has a couple of variations of an ear for the for > > web servers such as Webspear, Weblogic etc... To handle this, we use > > Maven profiles which only include the web server's required files before > > packaging. Is there a way to create these variations with at the > > same time, producing, say, three ears, one for each web server? I > > am guessing you could use classifiers, but I'm not sure how. > > You could use the invoker plugin to call the project with different > profiles > from some parent profile and use the classifier for the artifact. > > Or you could just move the profile stuff into separate projects that depend > on > the master pom and e.g. download it with the dependency plugin, explode it > and > then do an overlay with the changes. I have done that with the war plugin, > but I > think it might work with ears as well.. > > Manfred Moser > http://www.simpligility.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
