Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 29926 invoked from network); 26 Jun 2002 02:22:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Jun 2002 02:22:32 -0000 Received: (qmail 28472 invoked by uid 97); 26 Jun 2002 02:22:44 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 28437 invoked by uid 97); 26 Jun 2002 02:22:43 -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 28421 invoked by uid 98); 26 Jun 2002 02:22:43 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Tue, 25 Jun 2002 19:21:36 -0700 (PDT) From: costinm@covalent.net X-X-Sender: costin@costinm.sfo.covalent.net To: Jakarta Commons Developers List Subject: RE: [commons-logging] New services API In-Reply-To: <20020625170312.V39372-100000@icarus.apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 25 Jun 2002, Craig R. McClanahan wrote: > I like the concept of abstracting out this logic (mabye we could call it > "discovery" to avoid name conflict with the "services" package already in > the sandbox?). The design pattern is definitely useful and reusable. > > I think making commons-logging depend on it would need a 1.1 release, with > release notes that prominently highlighted the new dependency. And that > would need to wait for a 1.0 release of the discovery thingie. > > You can put the code into the sandbox without a vote (I'll make sure you > have appropriate karma - every Jakarta committer gets that if they want > it). You can add me as a maintainer on your status file. To get into > commons proper, though, it'll need a formal vote. I'd suggest doing the > grunt work in the sandbox first. You can add me to the list - and maybe we can vote on it quickly, it seems there are already 3 commiters and is a component that is has the potential to be shared by more ( or at least is already duplicated in at least 4 projects ). Costin -- To unsubscribe, e-mail: For additional commands, e-mail: