Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
From: Arnaud Bailly <abailly@oqube.com>
To: continuum-users@maven.apache.org
Subject: Re: Maven2 release process in Continuum
In-Reply-To: <5A0FC4D52198F24F9CC6CFE822269363012A9616@agits-mail03.ag-it.com>
	(Johan Iskandar's message of "Wed, 18 Jul 2007 16:28:26 +0700")
Organization: OQube
References: <5A0FC4D52198F24F9CC6CFE822269363012A9616@agits-mail03.ag-it.com>
Date: Wed, 18 Jul 2007 15:11:36 +0200
Message-ID: <87r6n5svp3.fsf@oqube.oqube.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

"Johan Iskandar" <Johan.Iskandar@ag-it.com> writes:
>
> BUT, I wonder whether maven encourages an explicit declaration of
> version in the pom(just as the above assumption)? Please advise? Also
> why does it use SNAPSHOT instead of build version..(the letter z in my
> example)?
>

Yes, maven enforces an explicit declaration of version in a
POM. AFAICT, maven does not validate a POM which does not contain a
version number, so you cannot build it. Maven is rather agnostic about
version numbering schemes, but understand quit well x.y.x notation
that is used in version ranges for dependencies management.

SNAPSHOT is a special qualifier for version that says we are
building a (surprise !) snapshot development version of a piece of
software. Snapshots are handled differently from standard versions, in
that:
 - when you install/deploy a project labelled SNAPSHOT, the artifact
 is actually deployed with a build number and the repository is
 updated to reflect the latest snapshot
 - you can define different repositories for deploying/downloading
 artifacts.

HTH=20
--=20
OQube < software engineering \ g=E9nie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com