lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [lucenenet] NightOwl888 commented on issue #396: Idea on how to handle manually editing the docs files while keeping the automated conversion
Date Thu, 26 Nov 2020 17:31:13 GMT

NightOwl888 commented on issue #396:

   I have converted the `JavaToMarkdownConverter` to a dotnet tool (currently at
simply named `javadoc2markdown` and set up an official NuGet feed to download it from at
   To install the latest version of the tool in the scripts to a local path, just run the
   dotnet tool install javadoc2markdown --add-source
--tool-path ./
   Then run the command:
   The parameters are exactly the same as they were before.
   Then to clean up, run the command:
   dotnet tool uninstall javadoc2markdown --tool-path ./
   You might want to put that last line in a finally block to ensure the script is re-runnable
in the case of an exception.
   The GitHub repo is only meant to be temporary until an Apache repo is set up for it. I
haven't yet removed the tool from this repo, but I suggest to do so and update the scripts
before doing any branching. 
   The changes I made are enough to decouple the docs build scripts from any specific version
of the tool, but the `JavaDoc2Markdown` tool's build and upload to the feed could be fully
automated by referencing `Nerdbank.GitVersioning` and copying the `azure-pipelines.yml` and
related files from [Morfologik.Stemming](
(minus the test stage, we don't need that). We would also need to remove some of the [custom
from the `version.json` file, which is what configures `Nerdbank.GitVersioning` and remove
the explicit `<Version>` property from the project file.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message