Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 59886 invoked from network); 19 Jan 2003 19:17:01 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 19 Jan 2003 19:17:01 -0000 Received: (qmail 6733 invoked by uid 97); 19 Jan 2003 19:18:25 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 6717 invoked by uid 97); 19 Jan 2003 19:18:24 -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 6705 invoked by uid 98); 19 Jan 2003 19:18:23 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Sun, 19 Jan 2003 14:16:57 -0500 (EST) From: Henri Yandell X-X-Sender: To: Jakarta Commons Developers List Subject: Re: [lang] Bug #14357 Stack trace order In-Reply-To: <004601c2bfee$cf833780$9f1f29d9@oemcomputer> 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 Sun, 19 Jan 2003, Stephen Colebourne wrote: > I would like to treat this as a bug, and just reverse the order to the > 'correct' one (compliant with JDK 1.4 and others). +1, though I expect the deprecation police to throw a tizzy. > Otherwise, I think that a static setStackOrderHighestToLowest(boolean) > method is better than a system property. Acceptable [as is the property one] but I'd still want to reverse the default even if we did add some kind of way to modify the order. So it's more a question of: Should we keep the current way in anyway? Hen -- To unsubscribe, e-mail: For additional commands, e-mail: