lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vitaly Funstein <vfunst...@gmail.com>
Subject Re: ReferenceManager.maybeRefreshBlocking() should not be declared throwing InterruptedException
Date Sun, 22 Jul 2012 01:21:46 GMT
Yeah, this is in 4.0-ALPHA. What should I updated my Maven dependency to
get the latest snapshots, instead - if that's where the fix is?

On Sat, Jul 21, 2012 at 4:16 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> Thanks Vitaly.
>
> I think you are looking at an older 4.x/5.x version?  We recently
> removed declaration of this (unchecked) exception... (LUCENE-4172).
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Fri, Jul 20, 2012 at 11:26 PM, Vitaly Funstein <vfunstein@gmail.com>
> wrote:
> > This probably belongs in the JIRA, and is related to
> > https://issues.apache.org/jira/browse/LUCENE-4025, but
> > java.util.Lock.lock() doesn't throw anything. I believe the author of the
> > change originally meant to use lockInterruptibly() inside but forgot to
> > adjust the method sig after changing it back to lock().
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message