You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great point, thank you for clarifying. We also intend on adding a demo template, but I think we can improve the instructions here about the other packages required.
I'm also wondering if it would be helpful to create a "Lucene.Net.StarterPack" NuGet package that has no code itself but brings in common Lucene.NET packages like Analysis.Common, and possibly some common others like QueryParser, Facet, and Highlighter... we could then use this single package in the quick start on the homepage.
I'm also wondering if it would be helpful to create a "Lucene.Net.StarterPack" NuGet package that has no code itself but brings in common Lucene.NET packages like Analysis.Common, and possibly some common others like QueryParser, Facet, and Highlighter... we could then use this single package in the quick start on the homepage.
Being that in later versions of Lucene, they brought the StandardAnalyzer back into the core library (likely based on user feedback such as this), I would say no, we don't need to do that. We will eventually upgrade our way out of this issue.
In fact, I wonder if we should even bother addressing this at all. Whatever the solution is, we will need to back it out when we upgrade. It seems like a waste of our limited resources to spend time doing something that will cost more time later.
Is there an existing issue for this?
Describe the documentation issue
The demo app on https://lucenenet.apache.org/ does only compile after adding the package Lucene.Net.Analysis.Common.
Additional context
No response
The text was updated successfully, but these errors were encountered: