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: [email protected]
For additional commands, e-mail: [email protected]
