[
https://issues.apache.org/jira/browse/LUCENE-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-9577.
-----------------------------------
Resolution: Fixed
I merged the PR and adapted the Jenkins jobs to call the new tasks.
As the documentation build folder changed, I also adapted the Jenkins Javadoc
output folder for archiving.
> Move HTML Documentation to a separate subproject
> ------------------------------------------------
>
> Key: LUCENE-9577
> URL: https://issues.apache.org/jira/browse/LUCENE-9577
> Project: Lucene - Core
> Issue Type: Task
> Components: general/build
> Affects Versions: master (9.0)
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently Lucene/Solr have some subdirectory "site" containing some fragments
> for CHANGES.txt formatting and the Markdown to produce the site. The global
> documentation for both Lucene and Solr should be built with its own
> subproject {{:lucene:documentation}} and {{:solr:documentation}}.
> I will provide a PR that does the following:
> - Move Changes.html formatting scripts to gradle subfolder, so they are
> correctly shared between Lucene and Gradle and allows to split project
> (currently they live in Lucene only)
> - Move the site contents with correct names a {{src/assets}},
> {{src/markdown}} into the new documentation projects
> - Make packaging of documentation in the projects build.gradle.
> {{:lucene:documentation:assemble}} should assemble the documentation (same
> for Solr) and export it as configuration
> - The main packaging will use the artifacts provided to put it into TGZ. Also
> Release manager can build documentation using the above gradlew calls.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
