uschindler commented on pull request #501: URL: https://github.com/apache/solr/pull/501#issuecomment-1009849683
I think for the solr:validateConfigFileSanity test you can do the same: Just resolve the version at runtime of task. As this is a handwritten task we can easily use a provider. Maybe make a more generic provider available in the same way like you did before and let the JVMAgrumentProvider just call it. So solr:validateConfigFileSanity may be fixed by that. SHould I look into that or do you want to check this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
