maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Laird Nelson <>
Subject Re: What's better, properties or configuration
Date Sat, 26 Jan 2013 16:55:37 GMT
On Sat, Jan 26, 2013 at 12:10 AM, Joachim Durchholz <>wrote:

> E.g.
>   <properties>
>     <maven.compiler.source>1.7</**maven.compiler.source>
>     <>1.7</**>
>   </properties>
> vs.
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.**plugins</groupId>
>         <artifactId>maven-compiler-**plugin</artifactId>
>         <version>3.0</version>
>         <configuration>
>           <source>1.7</source>
>           <target>1.7</target>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>

Properties in cases where you want to easily vary things from the command
line; configuration where you want to lock it down.  Obviously the other
considerations (like profiles) are worth considering as well.

I've found just for reducing the boilerplate that I err on the side of
properties for simple "no, dammit, I don't want source to be 1.3"
settings--if I'm not concerned with multiple executions, etc.

One thing I've never been clear on is the override mechanisms: if I have a
super pom with <properties> in it, a sub pom with <properties> in it that
has some overrides in it, and a command line property, I would hope that
the command line stomps on both the sub and super pom property values in
question.  I haven't sat down and rigorously tested this.



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