What's better, properties or configuration

2013-01-26 Thread Joachim Durchholz
E.g. properties maven.compiler.source1.7/maven.compiler.source maven.compiler.target1.7/maven.compiler.target /properties vs. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId

Re: What's better, properties or configuration

2013-01-26 Thread Anders Hammar
Config is the way to go. I don't even think that pom properties work, it has to be Java system properties (i.e. specified on command line). /Anders On Sat, Jan 26, 2013 at 9:10 AM, Joachim Durchholz j...@durchholz.org wrote: E.g. properties

Re: What's better, properties or configuration

2013-01-26 Thread Doug Douglass
@Anders, on the contrary, pom properties work quite well. @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. We do this in our poms, and I've seen it in others, for things like

Re: What's better, properties or configuration

2013-01-26 Thread Laird Nelson
On Sat, Jan 26, 2013 at 12:10 AM, Joachim Durchholz j...@durchholz.orgwrote: E.g. properties maven.compiler.source1.7/**maven.compiler.source maven.compiler.target1.7/**maven.compiler.target /properties vs. build plugins plugin

Re: What's better, properties or configuration

2013-01-26 Thread Joachim Durchholz
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

Re: What's better, properties or configuration

2013-01-26 Thread Stephen Connolly
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

Re: What's better, properties or configuration

2013-01-26 Thread Mirko Friedenhagen
I use properties a lot especially in parent poms and especially for versions of dependencies and plugins. By this testing new versions in real projects is much easier. Regards Mirko -- Sent from my mobile On Jan 26, 2013 9:10 AM, Joachim Durchholz j...@durchholz.org wrote: E.g. properties

Re: What's better, properties or configuration

2013-01-26 Thread Jörg Schaible
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