You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by Itamar Syn-Hershko <it...@code972.com> on 2017/05/05 10:46:00 UTC

Re: Nuget v3

Thanks, it's my blog, I'll get that fixed :)

--

Itamar Syn-Hershko
Freelance Developer & Consultant
Elasticsearch Partner
Microsoft MVP | Lucene.NET PMC
http://code972.com | @synhershko <https://twitter.com/synhershko>
http://BigDataBoutique.co.il/

On Sun, Mar 5, 2017 at 9:23 PM, David Lewis <da...@gmail.com> wrote:

> In the Beta anouncement article on Code972 the provided URI for the MyGet
> repository
> https://www.myget.org/feed/lucene-net/package/nuget/Lucene.Net only works
> for NuGet 2.0.  I found in the comments that another developer was having
> the same problem as I was using this repository.  The correct V3 repository
> URI  is https://www.myget.org/F/lucene-net/api/v3/index.json I would have
> added it into the comments for the article but the comments were closed.
>

Re: Nuget v3

Posted by David Lewis <da...@gmail.com>.
Cool.  Thank you and the other contributors for all of the work you've done
on getting Lucene.NET ready for release.

Once I get some time I would like to help.

On Fri, May 5, 2017, 5:46 AM Itamar Syn-Hershko <it...@code972.com> wrote:

> Thanks, it's my blog, I'll get that fixed :)
>
> --
>
> Itamar Syn-Hershko
> Freelance Developer & Consultant
> Elasticsearch Partner
> Microsoft MVP | Lucene.NET PMC
> http://code972.com | @synhershko <https://twitter.com/synhershko>
> http://BigDataBoutique.co.il/
>
> On Sun, Mar 5, 2017 at 9:23 PM, David Lewis <da...@gmail.com> wrote:
>
> > In the Beta anouncement article on Code972 the provided URI for the MyGet
> > repository
> > https://www.myget.org/feed/lucene-net/package/nuget/Lucene.Net only
> works
> > for NuGet 2.0.  I found in the comments that another developer was having
> > the same problem as I was using this repository.  The correct V3
> repository
> > URI  is https://www.myget.org/F/lucene-net/api/v3/index.json I would
> have
> > added it into the comments for the article but the comments were closed.
> >
>