Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 710 invoked from network); 12 Aug 2002 09:42:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Aug 2002 09:42:15 -0000 Received: (qmail 25726 invoked by uid 97); 12 Aug 2002 09:42:49 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 25710 invoked by uid 97); 12 Aug 2002 09:42:48 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 25698 invoked by uid 98); 12 Aug 2002 09:42:48 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <129f01c241e4$258f6a60$9865fea9@spiritsoft.com> From: "James Strachan" To: "Jakarta Commons Developers List" References: Subject: Re: [JJAR] New features Date: Mon, 12 Aug 2002 10:39:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Geir Magnusson Jr." > On 8/12/02 1:41 AM, "James Strachan" wrote: > > > ----- Original Message ----- > > From: "Geir Magnusson Jr." > >> This presents an interesting question - can a package have dependencies > >> that change over time? Suppose a dependency had a bug, and the authors of > >> the dependency released a fix. I guess for now, we just punt and say that > > a > >> local definition in the local repo is definitive for any operation, and > > then > >> later add a 'refresh' op that updates the local repo jars and descriptor. > > > > FWIW there's a SNAPSHOT feature in Maven whereby a project can be dependent > > on the latest, greatest snapshot release, so as bugs get fixed you > > automatically get the latest version. So a verion of 'SNAPSHOT' rather than > > 1.2-b4 or whatever, just means the latest release added to the repo. Great > > for development though this mechanism probably shouldn't be used for actual > > releases though. > > I saw that - it's pretty cool. > > I meant refresh the versions you currently have, mainly for the case where a > production version of something like a dependency gets superceded by an > upgrade for some reason. Yes - whenever the snapshot is updated and you do a Maven build, your local repo is updated (if you're online) with the latest snapshot from the remote repo. Though typically snapshot builds will ultimately used for nightly builds of CVS HEAD. So maybe some alias like LATEST which could be used for the latest release? Maybe some kinda wildcards could be used for dependency versions. Like 1.2.* for any release starting with 1.2.0 or 1.2.4> for any release from 1.2.4 onwards or something? Then as new releases are made there's no need to hunt around your dependency files and keep them up to date. I'm sure both Maven and JJAR could benefit from something like this. Maybe even some kinda Ant-style includes/excludes patterns? ant 1.4.1>, 1.5.* 1.4.1.2 James ------- http://james.weblogger.com/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: For additional commands, e-mail: