Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <20155986.post@talk.nabble.com>
Date: Fri, 24 Oct 2008 12:00:05 -0700 (PDT)
From: jaxzin <Brian.R.Jackson@espn3.com>
To: users@archiva.apache.org
Subject: TTL caching for metadata?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


All, when we run our releases we run Maven with the -U command.  This causes
Maven to query our Archiva instance for the maven-metadata.xml for
everything (plugins/parent/dependencies) that don't have explicit version. 
Unfortunately Archiva always goes back to the remote repositories when this
happens which lately has slowed our builds.  Is there a way to tell Archiva
to only check for new metadata once a day rather than whenever a Maven
client requests it?

P.S. The reason we run with -U command is because we have an internal POM
inheritance hierarchy that specifies parent versions with RELEASE so we can
make company-wide or department-wide tweaks to our build process and all
projects receive the changes implicitly.  But I don't necessarily need the
-U checking to go out to central or our other remote repositories.
-- 
View this message in context: http://www.nabble.com/TTL-caching-for-metadata--tp20155986p20155986.html
Sent from the archiva-users mailing list archive at Nabble.com.