maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <>
Subject Re: What's better, properties or configuration
Date Sat, 26 Jan 2013 18:04:41 GMT
My rule of thumb.

If you only need the value in one place... Don't use a property, they cause
more trouble than they're worth
If you need the same value in two or more places, the problems with
properties are less than the risk of being out of sync, so use the property.

On Saturday, 26 January 2013, Joachim Durchholz wrote:

> Am 26.01.2013 16:45, schrieb Doug Douglass:
>> @Anders, on the contrary, pom properties work quite well.
> I concur. I've used both approaches, and both did exactly what they were
> supposed to (verified by checking Maven output at "debug" verbosity).
>  @Jo, one consideration I think you missed is when configuring several
>> plugins with the same value it's handy (best?) to have that value
>> maintained in a single location.
> Right, I forgot to add that one.
> I'm setting UTF8 via property because (a) I routinely use UTF-8 for all
> sources and (b) more than one plugin uses that property and complains if
> the character set isn't set.
> > We do this in our poms, and I've seen it
>> in others, for things like file encoding and java source level that effect
>> several plugins.
> Java source level affects multiple plugins?
> Hm... oh, yes, I guess it's relevant for style checkers and such. I
> haven't had need for that yet, so I missed that the Java version is
> probably really best set via properties.
> Thanks, that settles it :-)
> (unless somebody comes along with entirely new aspects to consider)
> Regards,
> Jo
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message