Return-Path: 
 <hbase-dev-return-17544-apmail-hadoop-hbase-dev-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org
Received: (qmail 69210 invoked from network); 14 Feb 2010 01:43:36 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 14 Feb 2010 01:43:36 -0000
Received: (qmail 8699 invoked by uid 500); 14 Feb 2010 01:43:36 -0000
Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org
Received: (qmail 8653 invoked by uid 500); 14 Feb 2010 01:43:36 -0000
Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hbase-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hbase-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hbase-dev@hadoop.apache.org>
List-Id: <hbase-dev.hadoop.apache.org>
Reply-To: hbase-dev@hadoop.apache.org
Delivered-To: mailing list hbase-dev@hadoop.apache.org
Received: (qmail 8643 invoked by uid 99); 14 Feb 2010 01:43:36 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 01:43:36 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [209.85.222.174] (HELO mail-pz0-f174.google.com)
 (209.85.222.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 01:43:28 +0000
Received: by pzk4 with SMTP id 4so4030224pzk.5
        for <hbase-dev@hadoop.apache.org>;
 Sat, 13 Feb 2010 17:43:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.114.248.23 with SMTP id v23mr2250110wah.189.1266111786268;
	Sat, 13 Feb 2010 17:43:06 -0800 (PST)
In-Reply-To: <75CD8047-106A-4D31-AC3D-6BEF5F41AF60@aconex.com>
References: <3741C613-B9B6-4472-961A-608B30FA049F@aconex.com>
	 <4B765BFD.2080103@gmail.com>
	 <1c5747851002130003r2da1b8d2sc1bff83426e786f3@mail.gmail.com>
	 <78568af11002130010g4bb8682clc024ae1816c52e16@mail.gmail.com>
	 <4B766212.5020506@gmail.com>
	 <4aa34eb71002130129x4c7cb728tcc3877a01c9cbc6f@mail.gmail.com>
	 <4B767488.7050207@gmail.com>
	 <4aa34eb71002130151w4b140787sdc1ea105d3758b2c@mail.gmail.com>
	 <7c457ebe1002130211nfcb5e5ew7e76d7370d026ef1@mail.gmail.com>
	 <75CD8047-106A-4D31-AC3D-6BEF5F41AF60@aconex.com>
Date: Sun, 14 Feb 2010 12:43:06 +1100
Message-ID: <7c457ebe1002131743s77339a6ene97bee9ee21ea7cc@mail.gmail.com>
Subject: Re: Moving to Maven (HBASE-2099)
From: Dan Washusen <dan@reactive.org>
To: hbase-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0016e64ddeae44374e047f859f5d
X-Virus-Checked: Checked by ClamAV on apache.org

--0016e64ddeae44374e047f859f5d
Content-Type: text/plain; charset=ISO-8859-1

I stand corrected.  Maven checks for snapshot updates once a day (according
to that link below)...

On 14 February 2010 12:26, Paul Smith <psmith@aconex.com> wrote:

>
> On 13/02/2010, at 9:11 PM, Dan Washusen wrote:
>
> > Maven provides a "-o" argument and Ivy provides a "-Doffline=true"
> > property.  I haven't used the Ivy variant but if you're using SNAPSHOT
> > dependencies it makes the build a lot quicker.  I usually do an
> infrequent
> > online build then do the rest in offline mode...
> >
> > Maven also provides a "snapshot policy" that can be used to define the
> > interval between snapshot checks.  For example, "always", "daily",
> > "interval:<in minutes>" or "never"...
> >
> http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_snapshots
> >
>
> As I understand it, I think the Maven default setting is no more than once
> or twice a day to check for snapshot updates.  I wonder if the current ivy
> setting is just checking too often at the moment? (perhaps configurable).
>
> 'mvn -U' will force an update, I think '-o' for offline is a larger hammer
> that shouldn't be necessary.
>
> Paul

--0016e64ddeae44374e047f859f5d--