You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2026/09/10 13:52:00 UTC
[jira] [Commented] (SOLR-18069) Add test for testing maven solrj artifacts
[ https://issues.apache.org/jira/browse/SOLR-18069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113862#comment-18113862 ]
David Smiley commented on SOLR-18069:
-------------------------------------
FWIW I ran the PR manually copied to branch_9x and it passes, so the 9.11 release coming soon is compliant. For 10.1+ I'll work on seeing this through.
> Add test for testing maven solrj artifacts
> ------------------------------------------
>
> Key: SOLR-18069
> URL: https://issues.apache.org/jira/browse/SOLR-18069
> Project: Solr
> Issue Type: Test
> Reporter: Jan Høydahl
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We need a test or a smoke-test that actually tries to use the maven files generated for solrj. It would have caught the POM issue that happened with the "platform" module, see [https://github.com/apache/solr/pull/4039]
> An obvious location could be smoke tester, by adding a tiny soljr maven project somewhere in git and have smoke tester configure maven folder as local repo and execute ./mvnw wrapper.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org