lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [lucenenet] NightOwl888 edited a comment on issue #229: Updates docs build
Date Tue, 20 Aug 2019 03:18:34 GMT
NightOwl888 edited a comment on issue #229: Updates docs build
   Sorry, once again my message was posted before I was done with it. What happened to ENTER
always meaning CRLF instead of submit?
   > I've changed the docs home page to list the packages, i've categorized this by "Packages"
and "Tools" where demo + cli are under tools. I'm unsure about the UIMA package since I don't
know what project that belongs too so it's not actually part of the docs build right now which
means it doesn't currently link anywhere
   UIMA - probably not a thing. If it is possible, just leave it there, but make it generate
HTML comments so it is not visible.
   Demo - I thought it, but forgot to mention that these are all included in Lucene-CLI. What
I'd like to do is pull some of the documentation from that module into the CLI docs (maybe
I could just do that manually). I was also thinking that it would be simpler if instead of
linking to the code in the repo, just grab it and put it directly into the docs (MSDN style).
Each file is a standalone console app and would just need to be pasted inside of the docs.
   Come to think of it, I already put in some special tokens so only the code sample is grabbed
and none of the surrounding junk that isn't important for the sample. They are used by the
CLI tool itself to display the code on screen.
   So, basically instead of both Demo and CLI, we should just have CLI. But no problem keeping
the Tools category in case it grows.

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:

With regards,
Apache Git Services

View raw message