Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 49845 invoked from network); 3 Oct 2007 17:18:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 17:18:29 -0000 Received: (qmail 73298 invoked by uid 500); 3 Oct 2007 17:18:17 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 73265 invoked by uid 500); 3 Oct 2007 17:18:16 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 73254 invoked by uid 99); 3 Oct 2007 17:18:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 10:18:16 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 17:18:17 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Id7rB-0001k6-5s for continuum-users@maven.apache.org; Wed, 03 Oct 2007 10:17:57 -0700 Message-ID: <13023481.post@talk.nabble.com> Date: Wed, 3 Oct 2007 10:17:57 -0700 (PDT) From: noon To: continuum-users@maven.apache.org Subject: Re: Maven2 SNAPSHOT-artifacts in Continuum In-Reply-To: <13022688.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: rami.muurimaki@gmail.com References: <13022688.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org I knew it... once I decided to post something, I come up with something :) I got it working by adding the -U argument to the Maven goal attributes (goals: mvn clean test arguments: --batch-mode --non-recursive -U). I haven't figured out why I need to add this -U argument? Is it because Continuum refreshes the SNAPSHOT versions is some period of time or something else? noon wrote: > > After googling around without finding a proper solution I decided to post > a message in here. > > I'm trying to use Maven2 SNAPSHOT-versions during the development phase > where my webapp Maven2 project dependes on another Maven2 project's JAR. > When I deploy the SNAPSHOT JAR to Maven2 repository, it will be named e.g. > "myartifact-1.0-20071003.094654-1.jar" (this is the dependency that my > webapp uses). > > Using SNAPSHOT versions locally works just perfectly. Oh and I use "mvn > clean deploy" goals to deploy artifacts to the Maven repository. > > As a CI tool we're using Continuum (1.0.3). OK, after first SNAPSHOT > release Continuum works perfectly with the webapp but when I redeploy the > SNAPSHOT to Maven2 repository the deployed JAR will be named like > "myartifact-1.0-20071003.xxxxxx-2.jar" where the "xxxxxx" is some sort of > time stamp and "-2" is the build number, right? Sofar so good... However, > Continuum still uses the first SNAPSHOT version. Here's an excerpt from > Continuum build log: "resolved to version 1.0-20071003.094654-1". It never > uses any later deployed versions. > > Am I missing something or am I doing this SNAPSHOT releaseasing right? > > Thanks :) > -- View this message in context: http://www.nabble.com/Maven2-SNAPSHOT-artifacts-in-Continuum-tf4562937.html#a13023481 Sent from the Continuum - Users mailing list archive at Nabble.com.