I would strongly suggest that you move the distMgmt section to a corporate
parent pom instead. So when (if?) you change the urls, you just update the
parent pom (and yes, you do need to update the reference in any project
inheriting from it). Anything in your pom that could change depending on the
Hi
At my company we use properties in the global setting.xml which the
build is dependent. This make sense since our build is strictly within
our company and everyone uses the same maven installation
For instance:
(in setting.xml)
core
/ade/viper
(in pom.xml)
sdp
default
SDP Repository
f
Thanks for the advice. You could have proposed a solution instead of just a
criticism.
Sent from my iPhone
On Jan 19, 2011, at 4:02 AM, Anders Hammar wrote:
Very bad practice! The repositories defined in the pom MUST be possible for
other people (other projects depending on your artifacts) to
Very bad practice! The repositories defined in the pom MUST be possible for
other people (other projects depending on your artifacts) to resolve. Using
properties defined in settings.xml makes that impossible.
/Anders
On Wed, Jan 19, 2011 at 05:14, mjk wrote:
> Is it possible to use properties
