Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 95140 invoked from network); 9 Aug 2006 19:34:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Aug 2006 19:34:56 -0000 Received: (qmail 78040 invoked by uid 500); 9 Aug 2006 19:34:55 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 77839 invoked by uid 500); 9 Aug 2006 19:34:54 -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 77828 invoked by uid 99); 9 Aug 2006 19:34:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 12:34:54 -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 flamefew@gmail.com designates 66.249.82.238 as permitted sender) Received: from [66.249.82.238] (HELO wx-out-0506.google.com) (66.249.82.238) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2006 12:34:53 -0700 Received: by wx-out-0506.google.com with SMTP id t4so275345wxc for ; Wed, 09 Aug 2006 12:34:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rxx8PQgXp4MP1PaRlVwvfnQahjVQvFavyIvj34rD3h9FQ+oaU7KZ7vmKXAdy4ahrn7KaPWUpCWXUkULURIkMbDUXq6EKP52fPTQZ1lHCt0aRbr/reZmvSWf3T4k7ff/3F6MZQxsXwaHbYhsX7I5mMES/VCKb7vlxmRrrhaXZIbA= Received: by 10.78.175.8 with SMTP id x8mr592143hue; Wed, 09 Aug 2006 12:34:32 -0700 (PDT) Received: by 10.78.128.13 with HTTP; Wed, 9 Aug 2006 12:34:32 -0700 (PDT) Message-ID: <31cc37360608091234s772e2fd5r29bd341a314770cc@mail.gmail.com> Date: Wed, 9 Aug 2006 12:34:32 -0700 From: "Henri Yandell" To: "Jakarta Commons Developers List" Subject: Re: [Fwd: [FILEUPLOAD] Remove deprecated API] In-Reply-To: <44DA4C77.1050601@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44DA4C77.1050601@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > ---------- Forwarded message ---------- > From: "Jochen Wiedmann" > To: commons-dev@ws.apache.org > Date: Mon, 7 Aug 2006 01:22:23 +0200 > Subject: [FILEUPLOAD] Remove deprecated API > Hi, > > we have had two releases of commons fileupload with deprecated > methods. As the required changes for replacing the deprecated with the > recommended API are rather small (basically replace FileUpload with > ServletFileUpload and the DefaultFileItemFactory with > DiskFileItemFactory), I'd consider that tolerable for the users. Would > anyone reject, if I removed the deprecated stuff for 1.2? Yep, I object :) Our loose process is that we remove deprecateds in the next major release; not a minor. So if you choose to remove the deprecated API, you need to call it 2.0. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org