Hi Mike, I think we need it in the backwards break section of 3.0, because somebody may need to now add a catch block. For binary compatibility it has no effect (the IOException will be reported as unchecked), but for compile time.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Michael McCandless [mailto:[email protected]] > Sent: Sunday, November 01, 2009 2:13 AM > To: [email protected] > Subject: Re: Lock API, throwing IOException > > OK I just committed this to trunk! > > Mike > > On Sun, Nov 1, 2009 at 6:02 AM, Sanne Grinovero > <[email protected]> wrote: > > Thanks a lot! This makes error management much simpler. > > > > Sanne > > > > 2009/11/1 Michael McCandless <[email protected]>: > >> OK, this makes sense. I'll add it. > >> > >> Mike > >> > >> On Sat, Oct 31, 2009 at 9:43 AM, Sanne Grinovero > >> <[email protected]> wrote: > >>> Hello, > >>> I'm implementing a distributed directory based on Infinispan > >>> (www.jboss.org/infinispan) > >>> > >>> currently implementing the org.apache.lucene.store.Lock, > >>> I was wondering why is > >>> > >>> /** Returns true if the resource is currently locked. Note that one > must > >>> * still call {...@link #obtain()} before using the resource. */ > >>> public abstract boolean isLocked(); > >>> > >>> not throwing an IOException as other methods do? > >>> > >>> Could you please add it? It looks like it should be trivial, as all > >>> clients of this API are already declaring to throw the same Exception. > >>> > >>> Regards, > >>> Sanne Grinovero > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
