Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 62699 invoked from network); 14 Nov 2006 17:06:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Nov 2006 17:06:24 -0000 Received: (qmail 89710 invoked by uid 500); 14 Nov 2006 17:06:34 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 89686 invoked by uid 500); 14 Nov 2006 17:06:34 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Received: (qmail 89677 invoked by uid 99); 14 Nov 2006 17:06:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Nov 2006 09:06:34 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of chirino@gmail.com designates 64.233.162.201 as permitted sender) Received: from [64.233.162.201] (HELO nz-out-0102.google.com) (64.233.162.201) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Nov 2006 09:06:21 -0800 Received: by nz-out-0102.google.com with SMTP id v1so1048284nzb for ; Tue, 14 Nov 2006 09:06:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=LbNbtEvE/zdcBMyZvNrDxVNA4VDT5Ao0LBKPQgJ3YyMAOh1l9dIotwE0J+zEwbPOYpd8o7AS+oEt04eqIxfFaNQqvSQLFPQ9ZDSUstDKyN/+Zao08KxwKN+q9NF9yVLCRhH0fkGp1oHJyQm03nXY4zKzjoam+ehDlIYe0F2adjg= Received: by 10.78.26.9 with SMTP id 9mr1153874huz.1163523960353; Tue, 14 Nov 2006 09:06:00 -0800 (PST) Received: by 10.78.142.5 with HTTP; Tue, 14 Nov 2006 09:06:00 -0800 (PST) Message-ID: Date: Tue, 14 Nov 2006 12:06:00 -0500 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-dev@geronimo.apache.org Subject: Re: ActiveMQ POM In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <00f601c7080b$c77b5680$9cf1a8c0@ncanonizado> X-Google-Sender-Auth: f3efdc957b12a996 X-Virus-Checked: Checked by ClamAV on apache.org On 11/14/06, Guillaume Nodet wrote: > I think the main problem is that users will never > download newest versions. IMHO, this would be a bad > idea. yeah. > > On 11/14/06, Hiram Chirino wrote: > > Thanks Fritz! > > > > I knew there had to be a reason that I was just not aware of. What do > > you think would be the downsides of not using the special "SNAPSHOT" > > handling that maven provides? What if we tagged our SNAPSHOT builds > > with something like like "DEVELOPMENT" instead of "SNAPSHOT". > > > > I'm guessing that problem would go away, but what other ones would we get? > > > > On 11/14/06, Guillaume Nodet wrote: > > > This is also my experience. > > > If we just use the real version 4.2-SNAPSHOT > > > for example, it should also work and maven > > > should be able to change (*nearly*) all these > > > occurrences when using the release plugin. > > > > > > I say nearly, because in ServiceMix, there are > > > some edge cases where this fail (when including > > > the version in files other than pom.xml like artifacts > > > resources for example). > > > > > > On 11/14/06, Fritz Oconer wrote: > > > > Hi, > > > > > > > > I added ${activemq-version} instead of ${project.version} basically as a > > > > workaround for build failures due to differences in timestamp. If we use > > > > ${project.version} then it will require all activemq type artifacts > > > > (specified as in the parent pom.xml) to have the same timestamp > > > > as the parent. This becomes an issue when nightly-build deploy fails after > > > > some of the modules have been deployed causing some activemq modules to have > > > > different timestamp as the parent. We can change this back to using > > > > project.version but we need to make sure that nightly-build always deploys > > > > successfully or I wonder if there is another workaround for this? > > > > > > > > https://issues.apache.org/activemq/browse/AMQ-956 > > > > > > > > Regards, > > > > Fritz > > > > > > > > ----- Original Message ----- > > > > From: "Hiram Chirino" > > > > To: > > > > Sent: Tuesday, November 14, 2006 8:48 PM > > > > Subject: ActiveMQ POM > > > > > > > > > > > > > Howdy, > > > > > > > > > > I was wondering if anybody knows why we are using > > > > > "${activemq-version}" instead of "${project.version}" in our ActiveMQ > > > > > poms?? When doing a release build, it's easy to forget that you need > > > > > to updated the version in to places. Can't we just use the > > > > > "${project.version}" variable?? > > > > > > > > > > -- > > > > > Regards, > > > > > Hiram > > > > > > > > > > Blog: http://hiramchirino.com > > > > > > > > > > > > > > > > > -- > > > Cheers, > > > Guillaume Nodet > > > > > > > > > -- > > Regards, > > Hiram > > > > Blog: http://hiramchirino.com > > > > > -- > Cheers, > Guillaume Nodet > -- Regards, Hiram Blog: http://hiramchirino.com