[
https://issues.apache.org/jira/browse/SOLR-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199109#comment-16199109
]
Hoss Man commented on SOLR-11460:
---------------------------------
bq. FYI the {{dev-tools/scripts/addVersion.py}} script, ... maybe it should do
the same in test configs too?:
Why wouldn't we just use LATEST in all cases in that situation?
the only reason i can think of for not having LATEST in all our test configs is
-- as Mike alluded to -- explicit tests that we can correctly parse an (older)
numeric value into a costant. That sort of testing can be done with a
single-purpose config that uses a sysprop set by the test itself dynamically
based on the available values in the Version class
bq. Solr's {{validate}} target invokes ... this could be broadened or
copied/modified to address test configs.
+1
> review <luceneMatchVersion> values used in test-files
> -----------------------------------------------------
>
> Key: SOLR-11460
> URL: https://issues.apache.org/jira/browse/SOLR-11460
> Project: Solr
> Issue Type: Task
> Reporter: Christine Poerschke
> Priority: Minor
>
> Noticed that different test files use (unexpectedly) different
> {{<luceneMatchVersion>}} values. Details to follow.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
