Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 45009 invoked from network); 26 Jan 2002 17:48:52 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Jan 2002 17:48:52 -0000 Received: (qmail 56 invoked by uid 97); 26 Jan 2002 17:48:53 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 20 invoked by uid 97); 26 Jan 2002 17:48:53 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 9 invoked from network); 26 Jan 2002 17:48:52 -0000 Reply-To: From: "Paulo Gaspar" To: "Lucene Developers List" , Subject: RE: Distributable JAR filename Date: Sat, 26 Jan 2002 19:04:59 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <04ba01c1a5dd$5ffa7710$6401a8c0@darden.virginia.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Erik - with a "k". Sorry Erik! And I thought I was careful with name spelling, after having so many people calling me Paolo instead of PaUlo. =;o) > What I'm after is a way to pull in a dependency with no manual > intervention > such as renaming files, but this is an issue bigger than lucene-dev, and I > apologize for opening this can of worms here. CJAN and JJAR are > efforts to > accomplish this kind of thing and I've seen lots of talk about them on the > general/commons lists. Yes, I would say that the can of worms should be open at "general". I have no great magic bullet idea that solves this issue but I agree that we should find one. Please "open the can" at general and lets get everybody thinking about this. It is possible that guys like Sam Ruby (because of Gump), Geir (because of CJan/JJar) or some of other veterans have a clearer idea on how to solve this one. Have fun, Paulo > -----Original Message----- > From: Erik Hatcher [mailto:lists@ehatchersolutions.com] > Sent: Friday, January 25, 2002 9:18 PM > To: Lucene Developers List; paulo.gaspar@krankikom.de > Subject: Re: Distributable JAR filename > > > From: "Paulo Gaspar" > > > Eric, > > Erik - with a "k". > > > I do not see why having the version in the name makes upgrading harder. > > It doesn't necessarily make it harder - but it seemed out of sync > with other > Jakarta projects I'm familiar with although there is a discrepancy among > projects in how they deal with this issue. > > No point in belaboring this issue since its been rejected by lucene-dev. > > But if anyone cares to address the scenario I posed about > Lucene's own build > upgrading to JUnit 3.7 I'd love to hear how you'd do it. > > > A developer can always decide to rename the luceneXXXX.jar to lucene.jar > > all the time he upgrades and there is no trouble with configuration > > anymore. The effort to do this is minimal. > > What I'm after is a way to pull in a dependency with no manual > intervention > such as renaming files, but this is an issue bigger than lucene-dev, and I > apologize for opening this can of worms here. CJAN and JJAR are > efforts to > accomplish this kind of thing and I've seen lots of talk about them on the > general/commons lists. > > Erik > > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: