[
https://issues.apache.org/jira/browse/SOLR-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125324#comment-18125324
]
David Smiley commented on SOLR-18119:
-------------------------------------
I'm passionate about kicking this out of the gradle build! As to it's
language; seems keeping it script-y (Python) is a better trade-off than Java.
Agreed Java 25 may change the language equation but not for now. And even if
we did switch the language... we'd probably want to leverage the Java ecosystem
(libs) and not aim for byte-identical results.
> Changes.html generation is quietly skipped if python3 not found, can cause
> downstream tasks to fail confusingly
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-18119
> URL: https://issues.apache.org/jira/browse/SOLR-18119
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Assignee: Jan Høydahl
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> ChangesToHtmlTask will log a warning if python3 doesn't exist – but it does
> not fail.
> downstream tasks that (implicitly) depend on the existence of Changes.html
> will subsequently fail...
>
> {noformat}
> :solr:documentation:checkBrokenLinks
> :solr:solr-ref-guide:checkSiteLinks{noformat}
>
> This can be very confusing on jenkins boxes – such as our Windows jenkins
> build, which does not have python3 – when people don't know/realize that
> {{:solr:documentation:changesToHtml}} quietly did nothing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
