Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 45022 invoked from network); 28 Apr 2008 06:52:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Apr 2008 06:52:24 -0000 Received: (qmail 63009 invoked by uid 500); 28 Apr 2008 06:52:26 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 62810 invoked by uid 500); 28 Apr 2008 06:52:26 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 62799 invoked by uid 99); 28 Apr 2008 06:52:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Apr 2008 23:52:25 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.154.225.82] (HELO esmail.elsag.de) (62.154.225.82) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 28 Apr 2008 06:51:41 +0000 content-class: urn:content-classes:message Subject: RE: [Studio] Renaming 1.1.0 branch to 1.1.x MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Apr 2008 08:51:52 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Studio] Renaming 1.1.0 branch to 1.1.x Thread-Index: Acim8u69muOfV7hBRgSRE9RiaoKLUQCCOzHQ References: <98d8c0860804250555m13902bid2fcab3c44123e72@mail.gmail.com> <4811D6AF.2050601@apache.org> <1CBFBBB0-61F1-4436-846F-C276465A8D17@yahoo.com> From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Apache Directory Developers List" X-Virus-Checked: Checked by ClamAV on apache.org Hi David, David Jencks wrote: [snip] > Another strategy is to name it 1.1, and have the version either stay > at 1.1-SNAPSHOT (till the end of time)=20 not the best idea, since 1.1-SNAPSHOT means implicitly 1.1.0-SNAPSHOT. = If Maven has to resolve a transitive dep and one has 1.1-SNAPSHOT and = the other one is e.g. 1.1.1 the latter will win. I.e. even if you = already working towards release 1.1.42, 1.1.1 will stil be selected. = Learned this the hard way too ;-) > or 1.1.1-SNAPSHOT and > update it > after every release. Therefore this is the better solution. [snip] Just my 2c, J=F6rg