Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 13054 invoked from network); 7 Aug 2006 13:29:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Aug 2006 13:29:44 -0000 Received: (qmail 20446 invoked by uid 500); 7 Aug 2006 13:29:41 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 20364 invoked by uid 500); 7 Aug 2006 13:29:41 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 20352 invoked by uid 99); 7 Aug 2006 13:29:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 06:29:41 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of tcurdt@gmail.com designates 66.249.82.235 as permitted sender) Received: from [66.249.82.235] (HELO wx-out-0506.google.com) (66.249.82.235) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2006 06:29:40 -0700 Received: by wx-out-0506.google.com with SMTP id t4so283021wxc for ; Mon, 07 Aug 2006 06:29:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=pxKBH5EqUiVSTDM73ttdffsZBUa3Dy9atF1X0IIpqlvBBPYklZvlzJU1Fcandp8LDRsSTjl3N+M/clF8vuY6sDTJU0k8BzSm3BmWDPX1IqjGETS7ZX7Ewude19zXyFO64v7Vl2aUeU+AmkAj3OKiaK7/CG3LebVEZF09CUsL5kY= Received: by 10.78.183.8 with SMTP id g8mr2392468huf; Mon, 07 Aug 2006 06:29:19 -0700 (PDT) Received: by 10.78.178.14 with HTTP; Mon, 7 Aug 2006 06:29:19 -0700 (PDT) Message-ID: <98e4f1cd0608070629v3c7b7575pecbc455e07d632dc@mail.gmail.com> Date: Mon, 7 Aug 2006 23:29:19 +1000 From: "Torsten Curdt" Sender: tcurdt@gmail.com To: "Jakarta Commons Developers List" Subject: [jci] configuration MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: a1061327b946c495 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I am currently trying to figure out the configuration part of jci ...and at the moment I am really torn apart which way to go. Usually I am one of those that likes static typing ...which is what the plexus compiler API (and the javac implementation of jci) uses. Having a configuration class with setters like settings.setVerbose(boolean) ...but looking at the native eclipse compiler implementation (which is just using a map) settings.put(settings.OPTION, settings.OPTION_VALUE) I am really tempted to go that way. The interface would be so much easier and way more extensible. The compilers could pick the options they need and warn about options they don't understand. As very often the configuration does not come from a statically typed resource anyway (like a xml or properties file) the static API might not even that convenient at all. Opinions? cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org