[
https://issues.apache.org/jira/browse/SOLR-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055017#comment-18055017
]
David Smiley commented on SOLR-18092:
-------------------------------------
I wish we had some sort of integration test / CI job to catch this!
> ExternalPaths clinit errors when using test-framework in downstream projects
> ----------------------------------------------------------------------------
>
> Key: SOLR-18092
> URL: https://issues.apache.org/jira/browse/SOLR-18092
> Project: Solr
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Chris M. Hostetter
> Priority: Major
>
> Solr 10 (or maybe 9.10?) broke the ability to use Solr's {{test-framework}}
> in downstream projects to develop plugins, due to changes in the way
> {{ExternalPaths.SOURCE_HOME}} is initialized.
> The docs for this variable say the variable will be {{null}} in situations
> such as "the current context is a client code base using the test framework"
> – but the {{determineSourceHome()}} method used to initialize this variable
> was changed to throw an exception instead of returning null.
> ----
> Because this method is called on class loading, and because {{ExternalPaths}}
> is used pervasively in the {{test-framework}} code, there is no "code change"
> downstream projects can make to resolve these exceptions.
> Instead the one workaround I have identified for this back-compat break is
> for downstream packages to add some empty dummy directories and files to
> their test classpaths...
> {noformat}
> ./src/test/resources/solr/conf/
> ./src/test/resources/solr/test-framework/build.gradle
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
