Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 34711 invoked from network); 2 May 2002 13:12:19 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 May 2002 13:12:19 -0000 Received: (qmail 23024 invoked by uid 97); 2 May 2002 13:12:19 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@nagoya.betaversion.org Received: (qmail 22933 invoked by alias); 2 May 2002 13:12:19 -0000 Delivered-To: jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 22919 invoked by uid 97); 2 May 2002 13:12:19 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 22900 invoked by uid 98); 2 May 2002 13:12:18 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <413D422BB635D11197D200600814DE36151C55@EBP-SERVER> From: Ole Bulbuk To: 'Avalon Developers List' Subject: AW: AW: [OT] Jakarta: keeping track of it all Date: Thu, 2 May 2002 15:11:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > "only about some avalon interfaces". It took several years to > get those > hammered out that way. There's about 200 pages of docs on our website > describing why they interfaces are the way they are. > > It is _the_ central point, it is half of the added value > avalon has as a > project. > > It is a small thing in terms of code. It is *huge* in terms of thought > and man hours. You can express the contents of the "Design Patterns" > book in about 30 interfaces and as much default impls of those > interfaces. However, the book doesn't really belong inside a commons > package either. If the interfaces and the default implementations are *common* and don't depend on other projects they do. Where should they go else? Interfaces that should be used in almost every Java software should of course go into a very basic package. Maybe the next JDK would be a nice soulution. ;-))) > Every jakarta project is able to use Avalon Framework. the > dependency is > captured in a single jar file, which is a stable release, > which has been > a stable release for a long time, which doesn't impact > project size very > much, etc etc etc. AFAIK, commons is a project that by definition doesn't depend on other projects. If you don't want to give the interfaces fewer people will use them. Simple but true? Cheers, Ole -- Ole Bulbuk Tel.: 0331/74759/60 Ernst Basler + Partner Fax: 0331/74759/90 Tuchmacherstr. 47 E-Mail: mailto:ob@ebp.de 14482 Potsdam WWW: http://www.ebp.de -- To unsubscribe, e-mail: For additional commands, e-mail: