lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wyatt Barnett <wyatt.barn...@gmail.com>
Subject Re: Removing LuceneVersion.LUCENE_48 from external API?
Date Mon, 07 Nov 2016 14:02:36 GMT
I think making it an optional parameter sounds like a good idea on the
surface. How does the java library handle this?

On Thu, Nov 3, 2016 at 3:39 PM Itamar Syn-Hershko <itamar@code972.com>
wrote:

> Hey folks,
>
> I'm working on some demos, and one things that keeps popping up and to be
> frank gets quite annoying is the requirement to specify
> LuceneVersion.LUCENE_48 on all public APIs - opening a readers and writers,
> analyzers, etc.
>
> Since we only have one version release, and that concept is not going to be
> really useful anyway, what do you say we remove (or set a default value for
> it) on all public facing APIs?
>
> Cheers,
>
> --
>
> Itamar Syn-Hershko
> http://code972.com | @synhershko <https://twitter.com/synhershko>
> Freelance Developer & Consultant
> Lucene.NET committer and PMC member
>

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