maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raketemensch <>
Subject Re: Best way to handle a universal pom?
Date Wed, 09 May 2012 20:49:22 GMT
Well, that's why I'm asking for a best practice, I'm trying to avoid
antishness as much as possible.

However, I'm in charge of 400+ individual Maven projects, not counting all
the modules. If an environment changes, I'm not eager to load up 400+
individual pom files to make the required change, then commit them all, etc.

The profiles I'm looking to include look like this:



It's not something I can put into a settings.xml file, which I'd rather not
do anyway, since it would be a very big potential build-breaker. But at the
same time, we have 10+ individual environments, and I'd rather not pollute
each project pom with pages of this stuff, nor would I like to (As mentioned
earlier) update 400+ poms just because a server path changes.

Is there a better way to handle this?

(I appreciate any advice given)

View this message in context:
Sent from the Maven - Users mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message