Return-Path: 
 <users-return-130932-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-users-archive@www.apache.org
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CE4FBEE1E
	for <apmail-maven-users-archive@www.apache.org>;
 Sat, 26 Jan 2013 19:59:17 +0000 (UTC)
Received: (qmail 21781 invoked by uid 500); 26 Jan 2013 19:59:15 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 21692 invoked by uid 500); 26 Jan 2013 19:59:15 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 21684 invoked by uid 99); 26 Jan 2013 19:59:15 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 19:59:15 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of mfriedenhagen@gmail.com
 designates 209.85.219.52 as permitted sender)
Received: from [209.85.219.52] (HELO mail-oa0-f52.google.com) (209.85.219.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2013 19:59:10 +0000
Received: by mail-oa0-f52.google.com with SMTP id k14so844060oag.11
        for <users@maven.apache.org>; Sat, 26 Jan 2013 11:58:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        bh=Xo2VoBX09cngCbErqG3qHpwOi3JJ7nUMJ1UXVYGsbO8=;
        b=ebjTW6haC8ZOYZd7/qqhN3FVLWlUEcMK9S94qeYs9stTbmEHNMhguoE0Tjic0qWY3K
         yCjCxyCymzYy/ifoU+f9sHGqCMze458US10AdIZtcd/VZ44DQm6W2aFPrjGwS2l0hPuT
         qKBR3LJT/KR7aUQTRNiNvjcixJKiwl8ZDDlgaLRiTcNv5DZsN0fAyrOS7x4DrZRXIV1e
         IrJj5W9nIL9DIGdErQtIZ0JZxGy2UiAAU7H5EpWb363zHWBrluRzQekExZNE+riEj0Br
         ScGQaLbvmGovr8mT6F4eUj8QFRXv6Sl2HiOV7Hu9nw8totqjNjysXLM//jVE9VKx7lkz
         DEJQ==
MIME-Version: 1.0
X-Received: by 10.60.169.207 with SMTP id ag15mr7486974oec.120.1359230330242;
 Sat, 26 Jan 2013 11:58:50 -0800 (PST)
Received: by 10.182.250.199 with HTTP; Sat, 26 Jan 2013 11:58:50 -0800 (PST)
Received: by 10.182.250.199 with HTTP; Sat, 26 Jan 2013 11:58:50 -0800 (PST)
In-Reply-To: <51038F6F.9030402@durchholz.org>
References: <51038F6F.9030402@durchholz.org>
Date: Sat, 26 Jan 2013 20:58:50 +0100
Message-ID: 
 <CAK8jvqzPTMqrHOfGKy-SrDY2yT8APCqxhh+=v9BwhWp33B+LpQ@mail.gmail.com>
Subject: Re: What's better, properties or configuration
From: Mirko Friedenhagen <mfriedenhagen@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=bcaec550afdc00869804d4367979
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec550afdc00869804d4367979
Content-Type: text/plain; charset=UTF-8

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" <jo@durchholz.org> wrote:

> E.g.
>
>   <properties>
>     <maven.compiler.source>1.7</**maven.compiler.source>
>     <maven.compiler.target>1.7</**maven.compiler.target>
>   </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>
>
> I can see several points that might factor into a decision, but I'm not
> sure which of them are relevant in practice:
>
> - Configuration can be varied on a per-<execution> level, properties
> cannot. Not so relevant for compiling where you typically split each
> compiler run into a separate pom, more for other plugins.
> - Properties can be varied using profiles, configuration cannot.
> - At least for the compiler plugin, examples in the tutorials and docs
> invariably show the configuration approach. (Is there a reason why
> properties are generally not as good as configuration?)
> - Properties are FAR more compact.
> - When configuring a plugin, only a subset of its configuration is usually
> taken from properties, so once you need to configure, using properties does
> not give an advantage anymore.
> - Anything else?
>
> Regards,
> Jo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<users-unsubscribe@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--bcaec550afdc00869804d4367979--