Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 12073 invoked from network); 25 Jun 2002 05:12:56 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Jun 2002 05:12:56 -0000 Received: (qmail 17040 invoked by uid 97); 25 Jun 2002 05:13:10 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 17009 invoked by uid 97); 25 Jun 2002 05:13:09 -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 16997 invoked by uid 98); 25 Jun 2002 05:13:09 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Qmail-Scanner-Mail-From: baliuka@centras.lt via jim.skynet.vl X-Qmail-Scanner: 1.03 (Clean. Processed in 1.346772 secs) Message-ID: <005f01c21c06$f6768860$0111010a@user> From: "Juozas Baliuka" To: "Jakarta Commons Developers List" References: Subject: Re: [VOTE][Collections] Naming conventions Date: Tue, 25 Jun 2002 07:12:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I agree, new naming is better, but can't find message with Aaron's -1, I want to know his motivation before to vote. ----- Original Message ----- From: "Michael A. Smith" To: "Jakarta Commons Developers List" Sent: Tuesday, June 25, 2002 5:41 AM Subject: Re: [VOTE][Collections] Naming conventions > It's possible this has been drowned out by the recent maven > and "core/lang/util" discussions, so I'm sending this out for any other > comments/votes. > > regards, > michael > > > On Sat, 22 Jun 2002, Michael A. Smith wrote: > > There has been recent discussion on this list about forming naming > > conventions for the collections component to ensure consistency within > > the collections API as more and more collection "decorators" are added. > > The discussion culminated in a summary by Stephen: > > http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-dev@jakarta.apac he.org&msgId=366210 > > http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=102416074321189&w=2 > > http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg08316.html > > [use whatever archive you prefer] > > > > Since the changes are considered a product change, they are governed by > > the lazy consensus voting rules which state that approval is assumed > > until a -1 occurs (at which point it reverts to consensus). Aaron Bates > > has -1 the laziness, and thus this is now a consensus vote. Thus, we > > need 3 +1 votes and no -1 votes in order to adopt the proposal. [*] > > > > > > I'd like to start with my +1 for the proposal. It doesn't have any > > compatibility impact since almost all the code has been added since the > > last collections release, and will make usage of the API much more > > straightforward. Maintenance may require more effort, but the proposal > > allows for reducing the maintenance if required (i.e. move the static > > inner classes as top level classes in a subpackage). > > > > regards, > > michael > > > > [*] See: http://jakarta.apache.org/site/decisions.html > > > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: