[
https://issues.apache.org/jira/browse/SOLR-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835025#comment-16835025
]
Hoss Man commented on SOLR-13424:
---------------------------------
both sets of warnings come using {{org.asciidoctor}} code (either directly
execing when building the barebones HTML, or programatically to parse metadata
out of the files for building the nav data) which delegates to jruby where the
reflection lives...
https://github.com/jruby/jruby/issues/4834
https://github.com/jruby/jruby/issues/5559
...i'm not sure why the {{\-build-raw-pdf}} target doesn't generate the same
warnings, but i don't think there is much we can do about it until there is a
jruby fix
> Ref Guide PDF build throws Java warnings after requiring Java 11 on master
> --------------------------------------------------------------------------
>
> Key: SOLR-13424
> URL: https://issues.apache.org/jira/browse/SOLR-13424
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Priority: Major
>
> Since the {{master}} branch requires Java 11, the Ref Guide build has started
> throwing WARNINGs that we should look into. Despite the WARNINGs, the PDF
> build finishes successfully and appears the same as usual.
> There are a couple moving parts here - first some classes [~hossman] wrote to
> validate links in the PDF, and second a .jar from the {{asciidoctor-ant}}
> project. I suspect some of these are related to Hoss' code and some are from
> the project that's doing the PDF conversion.
> I'll put the output from a Jenkins job in the comment to show the errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
