Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 23070 invoked from network); 2 Feb 2007 18:04:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Feb 2007 18:04:33 -0000 Received: (qmail 21656 invoked by uid 500); 2 Feb 2007 18:04:36 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 21623 invoked by uid 500); 2 Feb 2007 18:04:36 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 21612 invoked by uid 99); 2 Feb 2007 18:04:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 10:04:36 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2007 10:04:29 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4BA287141F2 for ; Fri, 2 Feb 2007 10:04:09 -0800 (PST) Message-ID: <1470665.1170439449306.JavaMail.jira@brutus> Date: Fri, 2 Feb 2007 10:04:09 -0800 (PST) From: "Doug Cutting (JIRA)" To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-793) Javadocs should explain possible causes for IOExceptions In-Reply-To: <13949234.1170411545499.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/LUCENE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469819 ] Doug Cutting commented on LUCENE-793: ------------------------------------- Should we add more precise exceptions for these cases, and add them to the 'throws' for these methods? If we make these subclasses of IOException then this would be back-compatible. > Javadocs should explain possible causes for IOExceptions > -------------------------------------------------------- > > Key: LUCENE-793 > URL: https://issues.apache.org/jira/browse/LUCENE-793 > Project: Lucene - Java > Issue Type: Bug > Components: Javadocs > Reporter: Michael McCandless > Assigned To: Michael McCandless > Priority: Minor > > Most methods in Lucene reserve the right to throw an IOException. This can occur for nearly all methods from low level problems like wrong permissions, transient IO errors, bad hard drive or corrupted file system, corrupted index, etc, but for some methods there are also more interesting causes that we should try to document. > Spinoff of this thread: > http://www.gossamer-threads.com/lists/lucene/java-user/44929 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org