[
https://issues.apache.org/jira/browse/SOLR-17969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18031279#comment-18031279
]
David Smiley edited comment on SOLR-17969 at 10/21/25 12:08 AM:
----------------------------------------------------------------
Users may be able to configure their environment to treat any JAR (solr-solrj)
as an _automatic_ module. But a Gradle build, for one, doesn't support that,
at least not without an [external
plugin|https://github.com/gradlex-org/extra-java-module-info?tab=readme-ov-file].
was (Author: dsmiley):
Users may be able to configure their environment to treat any JAR (solr-solrj)
as an _automatic_ module. But a Gradle build, for one, doesn't support that,
at least not with an [external
plugin|https://github.com/gradlex-org/extra-java-module-info?tab=readme-ov-file].
> JPMS module-info for SolrJ
> --------------------------
>
> Key: SOLR-17969
> URL: https://issues.apache.org/jira/browse/SOLR-17969
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Priority: Major
>
> For users that wish to use the Java 9 module system (JPMS) with SolrJ, this
> is a pain. SolrJ needs to either have a compiled module-info.java per JAR
> (ideal), or at least the "Automatic-Module-Name" metadata in its JAR
> otherwise (the bare minimum). Either way, "split packages" need to be
> addressed. With none of this addressed most users are stuck.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
