Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 93018 invoked from network); 26 Jun 2002 16:41:28 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 209.66.108.5 with SMTP; 26 Jun 2002 16:41:28 -0000 Received: (qmail 24245 invoked by uid 97); 26 Jun 2002 16:41:32 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 24228 invoked by uid 97); 26 Jun 2002 16:41:31 -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 24215 invoked by uid 98); 26 Jun 2002 16:41:30 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Wed, 26 Jun 2002 09:40:03 -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: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N On Wed, 26 Jun 2002 rsitze@us.ibm.com wrote: > Services is a noun, discovery is a verb... Agree that I've got a > collision. Also agree that services is overloaded. I'm going to create > the 'discovery' tree in the sandbox, rename the package to 'org.apache. > commons.service.discovery', and keep my class names as-is. We can > straighten any remaining concerns out in the sandbox. What about org.apache.commons.discovery ? Sandbox is fine, if you want to - but it would be good to have it stable and 1.0 soon, so we can start trying to get the various projects duplicating this functionality to eventually share it. Most cut&paste the code, but there are variations and class loader issues, it would be much simpler to have a consistent impl. Costin > > I'd also advocate that the existing (more heavy-weight/configurable) > service package be renamed to 'org.apache.commons.service.manager'. Olag, > what do you think? > > >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. > > >Craig -- To unsubscribe, e-mail: For additional commands, e-mail: