lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENENET-588) Create unified CLI tool to wrap all Lucene maintenance tools and demos for .NET
Date Tue, 13 Aug 2019 05:54:00 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shad Storhaug resolved LUCENENET-588.
-------------------------------------
    Resolution: Resolved

The {{lucene-cli}} tool is now on NuGet and can be installed using the command


{code:bash}
dotnet tool install lucene-cli -g --version 4.8.0-beta00006
{code}

The commands the tool supports can be explored by using the command

{code:bash}
lucene
{code}

See [the documentation|https://github.com/apache/lucenenet/blob/master/src/dotnet/tools/lucene-cli/docs/index.md]
for more info.

> Create unified CLI tool to wrap all Lucene maintenance tools and demos for .NET
> -------------------------------------------------------------------------------
>
>                 Key: LUCENENET-588
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-588
>             Project: Lucene.Net
>          Issue Type: New Feature
>          Components: Lucene.Net Core, Lucene.Net.Analysis.ICU, Lucene.Net.Analysis.Kuromoji,
Lucene.Net.Analysis.Stempel, Lucene.Net.Benchmark, Lucene.Net.Facet, Lucene.Net.Misc
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Assignee: Shad Storhaug
>            Priority: Minor
>             Fix For: Lucene.Net 4.8.0
>
>
> Since it is not possible to run a .NET Standard DLL as a console application, we need
to wrap Lucene's CLI utilities with a .NET Console application in order to make them readily
usable. Many of these tools are important to have on hand, especially the index maintenance
tools to upgrade, inspect, fix, split, merge, copy or delete segments, etc of indexes.
> There are many tools and they have inconsistent usage in Java. So, it makes more sense
for us to have a single unified CLI utility (like Microsoft's dotnet.exe tool) rather than
make a wrapper console application for each one. This also affords us the opportunity to make
the various parameters work consistently across tools.
> This project is already nearing completion - this task is just being created to tie all
of the CLI-related issues together so efforts are not duplicated on those individual tasks.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message