[
https://issues.apache.org/jira/browse/SOLR-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491676#comment-17491676
]
Uwe Schindler commented on SOLR-15556:
--------------------------------------
Hi,
after merging the PR to main, 9x and 9.0 the windows builds should succeed. I
also fixed the absolute path of the local javadocs to be a real URL.
There is one problem still exists: Refguide build prints a ton of warning for
every example file, because it can't find the tags in it. The problem is that
Windows doe snot support smbolic links, so when Git checks out, the .java files
below examples are all just plain text files containing the relative path to
the real file (this is how symlinks are internally looking like in Unix, just
files with the path the links refer to and a special attribute). On Windows the
git client checks them out like this.
Do we really need symlinks in Git checkouts? I don't care about the refguide
when developing windows support, but this could bring problems when committing
change. Luckily precommit does not fail, because rat seems to be excluded from
checking licenses of those fake files.
I will open a separate issue, the problem with the playbook files is resolved.
> Ref Guide Redesign Phase 3: Replace Jekyll
> ------------------------------------------
>
> Key: SOLR-15556
> URL: https://issues.apache.org/jira/browse/SOLR-15556
> Project: Solr
> Issue Type: Improvement
> Components: documentation
> Reporter: Cassandra Targett
> Assignee: Cassandra Targett
> Priority: Blocker
> Fix For: 9.0
>
>
> The final step of my grand vision for redesigning the Ref Guide is to look at
> replacing Jekyll with a different static site generator.
> The primary reason why is because Jekyll is designed for blog posts, not for
> sites with hundreds of static pages like ours. Back in 2017 when I chose it,
> it was relatively straightforward to implement, a lot of information was
> available in Jekyll docs and the internet in general to customize it, and it
> was one of the few that supported Asciidoc format.
> However now there are a lot more options, including some which are
> specifically designed for large multi-version documentation sites like the
> Ref Guide.
> Included with this will be reorganizing the on-disk organization of the ref
> guide files themselves.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
