This is what I would like to do but did not know what to expect, since so much more understanding of Maven would first need to be known to start, Is it possible? If so what potential issues?
On Mon, May 7, 2012 at 12:55 PM, Raketemensch <li...@libertylost.org> wrote: > When we were working with Ant, we created a build.xml file that had generic > targets that we needed in every build. This allowed us to change a single > file once, and have all 300+ builds be instantly updated. > > I'd like to do the same thing with Maven, but am concerned about creating > dependency issues, so I thought I would find out what would be the most > recommended way to go about doing it. > > Take profiles, for instance -- we use Wagon for SCPing files out to the > servers, so we have a profile set up for each environment (dev, qa, test, > prod, etc) that we currently include in every ear pom. > > Ideally we could just include these profiles in a single pom.xml and > include > it in all the projects. Opinions on the best way to do so? > > > Thanks, > Rake > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Best-way-to-handle-a-universal-pom-tp5691958.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
