Return-Path: 
 <dev-return-21000-apmail-maven-dev-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-dev-archive@www.apache.org
Received: (qmail 16894 invoked from network); 7 Jan 2004 14:34:01 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 7 Jan 2004 14:34:01 -0000
Received: (qmail 49448 invoked by uid 500); 7 Jan 2004 14:33:56 -0000
Delivered-To: apmail-maven-dev-archive@maven.apache.org
Received: (qmail 49416 invoked by uid 500); 7 Jan 2004 14:33:56 -0000
Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@maven.apache.org>
List-Subscribe: <mailto:dev-subscribe@maven.apache.org>
List-Help: <mailto:dev-help@maven.apache.org>
List-Post: <mailto:dev@maven.apache.org>
List-Id: "Maven Developers List" <dev.maven.apache.org>
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Delivered-To: mailing list dev@maven.apache.org
Received: (qmail 49400 invoked from network); 7 Jan 2004 14:33:55 -0000
Received: from unknown (HELO imtfinter.imtf.ch) (194.209.33.5)
  by daedalus.apache.org with SMTP; 7 Jan 2004 14:33:55 -0000
Received: from exchange.imtf.dmz [192.168.255.30]
	by imtfinter.imtf.ch
	with XWall v3.28 ;
	Wed, 7 Jan 2004 15:33:54 +0100
Received: by imtfexchange.imtf.ch with Internet Mail Service (5.5.2653.19)
	id <CN4XDT4R>; Wed, 7 Jan 2004 15:29:29 +0100
Message-ID: <DF7EC83D7AFBD411965B0008C7596EC5013845C1@imtfexchange.imtf.ch>
From: Maczka Michal <michal.maczka@imtf.ch>
To: "'dev@maven.apache.org'" <dev@maven.apache.org>
Subject: Some thought about SNAPSHOT dependencies.
Date: Wed, 7 Jan 2004 15:29:29 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

I am trying to find about the best practices related to SNAPSHOT
dependencies.
More and more I think about them I find that some things are rather not
clear and quite inconsistent.

There is one misleading thing: We often find in POMs (maven, maven plugins
do that):

<project>
  <pomVersion>3</pomVersion>
  <id>maven</id>
  <name>Maven</name>
  <currentVersion>1.1-SNAPSHOT</currentVersion>
                                    ^^^^^^^^^^^^^^^^^^^^

(I understand that <currentVersion>1.1-SNAPSHOT</currentVersion> denotes
that next release will be 1.1.)

It is possible to do

maven  jar:install   (will put maven-1.1-SNAPSHOT to repository) 
maven  jar:install-snapshot (will put maven-SNAPSHOT to repository)

Do we really intend to have two different types of snapshots? 

  <dependency>
     ..
     <version>1.1-SNAPSHOT</version>  (latest version of 1.1 branch)
  </dependency>

and

  <dependency>
     ..
     <version>SNAPSHOT</version> (latest version which can come from any of
the branches)
  </dependency>


If not maybe we can just have one single "install" goal instead of "install
and "install-snapshot"?
"jar:install" goal executed on project which current version is 1.1-SNAPSHOT
will deploy a snapshot version of jar.

Maybe indeed it is reasonable to lock usage of snapshot to one branch (like
1.0-SNAPSHOT, 1.1-SNAPSHOT)?

AFAIR there were some discussions about introducing something which denotes
latest released version (something like maven-RELEASE).
Maybe we should use those things together?

Any ideas?

Michal




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