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: QueryParser package on NuGet
Date Thu, 03 Nov 2016 15:33:48 GMT
Roger -- I'll take a look at the dependencies, it *should* be working that
way.

Longer-term, especially w/ multi-targeting, we probably need to look at
something fancier than teamcity's default packaging. I'm kind of partial to
FAKE for build scripts these days but I'm open to suggestion.

On Thu, Nov 3, 2016 at 11:31 AM Shad Storhaug <shad@shadstorhaug.com> wrote:

> It would if it were working right :).
>
> An example dependency chain:
>
> Lucene.Net.Analysis.Stempel --> Lucene.Net.Analysis.Common --> Lucene.Net
>
> These dependencies are not currently in the NuGet packages. When you
> install Lucene.Net.Analysis.Stempel, it should also install the
> dependencies.
>
> The external dependencies seem to be working, it is only the Lucene.Net
> (project-level) dependencies that are not. I suspect we might be only
> considering NuGet dependencies when generating the NuGet packages and
> ignoring project dependencies.
>
> Do note that when https://github.com/apache/lucenenet/pull/191 is merged
> that we will also likely need to alter how we release. I think we need to
> put multiple DLLs in each NuGet package (one for .NET 4.6 and one for .NET
> core). I'm not sure whether that functionality can work out of the box - in
> the past I have had to write scripts to get there. Of course, it all
> depends on what new functionality Roslyn/.NET core brings to the table and
> whether we can take advantage of it.
>
>
> -----Original Message-----
> From: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
> Sent: Thursday, November 3, 2016 8:57 PM
> To: dev@lucenenet.apache.org
> Subject: Re: QueryParser package on NuGet
>
> Shad -- thanks that package layout makes sense now.
>
> The OOTB behavior for the package generation should ride the dev's rails
> -- dependencies should be generated from the dependencies we've got in the
> csproj files; descriptions should come out of the assembly level attributes
> in the AssemblyInfo.cs files. Does that get you to where you want to be?
>
>
>
> On Thu, Nov 3, 2016 at 9:19 AM Shad Storhaug <shad@shadstorhaug.com>
> wrote:
>
> > Wyatt,
> >
> > No it doesn't for two reasons:
> >
> > 1. This is a port of Lucene, and we are doing our best to make our
> > packages 1-1 with version 4.8.0 of Lucene. Lucene has a Misc package,
> > so we should too.
> > 2. Some of the functionality in Misc depends on Analysis.Common.
> > Analysis.Common depends on Core. If we tried to move all of Misc to
> > Core, we would have a circular dependency between Analysis.Common and
> Core.
> >
> > Of course, some of the types in Misc are earmarked to go into Core in
> > a later version of Lucene, and when we update Lucene.Net we will
> > follow suit if any of those pieces need moving.
> >
> > Many of Lucene's namespaces and package names differ somewhat. For
> > example, both Suggest and Grouping contain namespaces that begin with
> > Lucene.Net.Search. But that doesn't mean they belong in the Core
> > package in the Lucene.Net.Search namespace. These are additional
> > pieces of functionality to extend search that can be added on if
> > needed. Misc mostly contains shared functionality that apparently didn't
> fit anywhere else.
> >
> > BTW - It seems none of the inter-package dependencies are included in
> > the packages. For example, every package should depend on Core, and
> > some depend on one another. These dependencies are still a WIP in some
> > cases. It would be nice if the devs had some control over how the
> > NuGet packages are generated so we could keep them up to date with the
> > codebase (dependencies, descriptions, etc).
> >
> > Thanks,
> > Shad Storhaug (NightOwl888)
> >
> > -----Original Message-----
> > From: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
> > Sent: Thursday, November 3, 2016 7:39 PM
> > To: dev@lucenenet.apache.org
> > Subject: Re: QueryParser package on NuGet
> >
> > Good catch Andrew -- I just added Misc to the build, it should be out
> > there in 2.5 hours or so after the build servers do their thing.
> >
> > Looking at the code, it seems like a lot of things reference the
> > Lucene.Net.Util.Fsc namespace which is in the misc project for some
> > reason
> > -- 127 to be exact. Does it make sense to move those functions to the
> core?
> >
> >
> >
> > On Thu, Nov 3, 2016 at 8:16 AM Roethinger, Alexander <
> > aroethinger@affili.net>
> > wrote:
> >
> > > Hi Wyatt,
> > >
> > > a noticed your comment on the need for Lucene.Net.Misc in your mail
> > below.
> > > It seems that AnalyzingInfixSuggester relies on Lucene.Net.Misc to
> load.
> > >
> > > When executing the following code:
> > >
> > > Lucene.Net.Store.Directory dir = FSDirectory.Open(path);
> > > StandardAnalyzer analyzer = new StandardAnalyzer(matchVersion);
> > > AnalyzingInfixSuggester suggester = new
> > > AnalyzingInfixSuggester(matchVersion, dir, analyzer);
> > >
> > >
> > > I get an "File or Assembly not found" exception:
> > > {"Die Datei oder Assembly \"Lucene.Net.Misc, Version=4.8.0.697,
> > > Culture=neutral, PublicKeyToken=null\" oder eine Abhängigkeit davon
> > > wurde nicht gefunden. Das System kann die angegebene Datei nicht
> > > finden.":"Lucene.Net.Misc, Version=4.8.0.697, Culture=neutral,
> > > PublicKeyToken=null"}
> > >
> > > To get around this, I compiled Lucene.Net.Misc from Lucene-Master
> > > and copied the DLL to my application directory and it works. But it
> > > would be nice to see an official package for Lucene.Net.Misc.
> > >
> > >
> > > Thanks and kind regards
> > > Alexander
> > >
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Wyatt Barnett [mailto:wyatt.barnett@gmail.com]
> > > Gesendet: Dienstag, 1. November 2016 03:29
> > > An: Itamar Syn-Hershko <itamar@code972.com>;
> > > user@lucenenet.apache.org; dev@lucenenet.apache.org
> > > Betreff: Re: QueryParser package on NuGet
> > >
> > > Sorry for the confusion -- the nuget pack doesn't automatically pick
> > > up any project, we need to add it to a list in the nightly project.
> > > Anyhow, projects have been added and the nightly is running now. We
> > > should see the packages out there in the next few hours barring
> > > another build timeout or me fat fingering things.
> > >
> > > While I was at it I added Memory, Analysis.Stempel and Suggest both
> > > as dedicated projects with their own builds but also to the nuget
> > > package generation.
> > >
> > > I looked at the other projects in the .sln as well. Misc just didn't
> > > seem to have anything one would want as an independent package,
> > > grouping seemed more ready but it doesn't have a test project. I can
> > > add them -- or any others -- when ready, just ping me.
> > >
> > > On Sat, Oct 29, 2016 at 2:47 PM Itamar Syn-Hershko
> > > <itamar@code972.com>
> > > wrote:
> > >
> > > > A better link: https://www.myget.org/gallery/lucene-net
> > > >
> > > > --
> > > >
> > > > Itamar Syn-Hershko
> > > > http://code972.com | @synhershko <https://twitter.com/synhershko>
> > > > Freelance Developer & Consultant Lucene.NET committer and PMC
> > > > member
> > > >
> > > > On Sat, Oct 29, 2016 at 9:31 PM, Itamar Syn-Hershko
> > > > <itamar@code972.com>
> > > > wrote:
> > > >
> > > > Hi Kirill,
> > > >
> > > > I'm assuming you are referring to our 4.8 release - it's currently
> > > > on MyGet and not nuget:
> > > > https://www.myget.org/feed/lucene-net/package/nuget/Lucene.Net
> > > >
> > > > However, it does seem like the QueryParser package isn't pushed
> there.
> > > >
> > > > *Wyatt*, any chance you can look into why is this? the project is
> > > > included in the sln file and I believe we already fixed that
> > > > before
> > > >
> > > > Thanks
> > > >
> > > > --
> > > >
> > > > Itamar Syn-Hershko
> > > > http://code972.com | @synhershko <https://twitter.com/synhershko>
> > > > Freelance Developer & Consultant Lucene.NET committer and PMC
> > > > member
> > > >
> > > > On Wed, Oct 26, 2016 at 3:15 AM, Kumar Krishnamoorthy <
> > > > kumar@seamlesscms.com> wrote:
> > > >
> > > > QueryParser is part of the core Lucene.Net assembly (
> > > > https://www.nuget.org/packages/Lucene.Net/).
> > > > Check under Lucene.Net.QueryParsers namespace.
> > > >
> > > >
> > > >
> > > >
> > > > Kumar Krishnamoorthy
> > > > Senior Product Developer
> > > >
> > > > Seamless | Empowering Digital Government
> > > > Phone: +613 9913 0020 <+61%203%209913%200020>
> <+61%203%209913%200020>
> > > > <+61%203%209913%200020>
> > > > E-mail: kumar@seamlesscms.com
> > > > www.seamlesscms.com
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Kirill Gribunin [mailto:gribunin@gmail.com]
> > > > Sent: Tuesday, 25 October 2016 10:53 PM
> > > > To: user@lucenenet.apache.org
> > > > Subject: QueryParser package on NuGet
> > > >
> > > > Is QueryParser package available via Nuget? I dont see it in the
> > > > list of available packages.
> > > >
> > > > Thanks,
> > > > Kirill Gribunin
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

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