Return-Path: 
 <users-return-126965-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 C785E9E41
	for <apmail-maven-users-archive@www.apache.org>;
 Tue, 24 Apr 2012 17:51:32 +0000 (UTC)
Received: (qmail 96598 invoked by uid 500); 24 Apr 2012 17:51:30 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 96363 invoked by uid 500); 24 Apr 2012 17:51:30 -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 96355 invoked by uid 99); 24 Apr 2012 17:51:30 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2012 17:51:30 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [207.183.49.139] (HELO production.artifact-software.com)
 (207.183.49.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2012 17:51:25 +0000
Received: from [192.168.3.170] (unknown [192.168.3.170])
	by production.artifact-software.com (Postfix) with ESMTP id 38A466A7A2D
	for <users@maven.apache.org>; Tue, 24 Apr 2012 13:51:04 -0400 (EDT)
Message-ID: <4F96E807.5080208@artifact-software.com>
Date: Tue, 24 Apr 2012 13:51:03 -0400
From: Ron Wheeler <rwheeler@artifact-software.com>
Reply-To: rwheeler@artifact-software.com
Organization: Artifact Software
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: users@maven.apache.org
Subject: Re: Parent POM entires and Effective POM
References: <1335281881522-5662422.post@n5.nabble.com>
 <CALy+7U=9vzwTJ9xjNgFdC8DphWHOdHq6avjK=Jq7D8D33e6msQ@mail.gmail.com>
 <1335285186146-5662592.post@n5.nabble.com>
 <CALy+7UkoOQTCb0mkVE3mGHD0CG3gmc9_j7AMAu-p3jxqeb_eVg@mail.gmail.com>
In-Reply-To: 
 <CALy+7UkoOQTCb0mkVE3mGHD0CG3gmc9_j7AMAu-p3jxqeb_eVg@mail.gmail.com>
Content-Type: multipart/mixed;
 boundary="------------000005040904060606020003"
X-Virus-Checked: Checked by ClamAV on apache.org

--------------000005040904060606020003
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 24/04/2012 1:24 PM, Wayne Fay wrote:
>> The parent has a 1.0 with no RELEASE OR SNAPSHOTs and the
>> child poms do not specify the version explicitly.
> Unless you are actively making a release, your version should almost
> always have the -SNAPSHOT qualifier appended to it. So if you are
> working on version 1.0, then your pom should show version 1.0-SNAPSHOT
> until the brief moment in time when you perform the release -- then it
> will be 1.0 -- and then immediately after it should bump to version
> 1.1-SNAPSHOT.
>
>> <spring.batch.admin>1.2.1.RELEASE</spring.batch.admin>
>> <spring.data.version>1.1.0.BUILD-SNAPSHOT</spring.data.version>
> I can't speak for everyone, but I am definitely not a fan of declaring
> dependency versions in a tag like this. It just makes things more
> complicated. When I open a pom, I want to find the version right there
> along with the GroupId and ArtifactId in<dependency>  or
> <dependencyManagement>. Managing versions with properties is not a
> best practice IMO.
If you have the same dependency in many modules and you want to ensure 
that all developers are using the same version since you likely want it 
as "provided", you will have a lot of maintenance to do.

My "management principle" is that version selection is a project 
management/team function and the developers of individual modules should 
not be concerned about the versions of shared dependencies. If they find 
a problem with the version selected by the team, then this should be 
raised to the team level.

Specifying versions in module level POMs opens the door to a module 
having the wrong version during the build which can show up as a method 
not found if the module was built with a version later than the one 
provided at runtime.

Ron

> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



--------------000005040904060606020003
Content-Type: text/plain; charset=us-ascii


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
--------------000005040904060606020003--