Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 23108 invoked from network); 21 Mar 2003 21:19:26 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 21 Mar 2003 21:19:26 -0000 Received: (qmail 24495 invoked by uid 97); 21 Mar 2003 21:21:16 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 24488 invoked from network); 21 Mar 2003 21:21:16 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 21 Mar 2003 21:21:16 -0000 Received: (qmail 22313 invoked by uid 500); 21 Mar 2003 21:19:16 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 22300 invoked from network); 21 Mar 2003 21:19:16 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 21 Mar 2003 21:19:16 -0000 Received: (qmail 76110 invoked from network); 21 Mar 2003 21:19:15 -0000 Received: from unknown (HELO apache.org) (127.0.0.1) by localhost.apache.org with SMTP; 21 Mar 2003 21:19:15 -0000 Message-ID: <3E7B81D8.4040308@apache.org> Date: Fri, 21 Mar 2003 22:19:20 +0100 From: Remy Maucherat Organization: ASF User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: [PROPOSAL] Distributing the .jar files as binaries in release References: <20030321205904.56291.qmail@web41205.mail.yahoo.com> In-Reply-To: <20030321205904.56291.qmail@web41205.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Mel Martinez wrote: > In general, I like the idea because there are numerous > projects out there that use specific jars from tomcat > and this would greatly ease access. There is some > discussion going on elsewhere in the community for > distributing jars with this kind of model. The idea > is that an application's expressed dependencies on 3rd > party packages can include a URL to the specific jar > (including version specification). Thus deployment > host platforms can automatically retrieve and resolve > dependencies without the application developer having > to be responsible for unpacking, repackaging a subset > of tomcat (or whatever) and then possibly having to > provide the subset on his/her own server. > > The caveats are that I don't know if there is > consensus yet on versioning format, there definitely > are too many competing package dependency schemes and > I'm not sure what the impact of jar refactoring will > be. > > Overall, though, I like the idea. If it's just to be used for build tools, then it's ok (and no need for a proposal, it just needs to get done). The trouble starts if users start thinking they can use that to upgrade to a newer release, just by upgrading one or two JARs (or ever worse, mixing components). Then there's trouble. Remy --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org