uschindler commented on PR #3261: URL: https://github.com/apache/solr/pull/3261#issuecomment-2730591034
Hi, ok makes sense. Generally I agree to move the Gradle build at some point to kotlin, but I don't see this as an important step. This should be done together with Lucene to again make use of each other. Generally the Lucene (and Solr build) was invented by @dweiss. I don't think that it is a simple replacement, because there is a lot of special thing especially to correctly compile MR-JARS, JavaModule-System builds (not correctly supported in Gradle at all, too much magic that breaks heavily). I was not aware that the issues come from the kotlin compiler for the user code, sorry. If that's the only issue I think the compiler-config in the runtime-java-home support can possibly be adapted to work correct witzh alternative JDKs. The problem is maybe only that some information is not exposed by our hack that's needed by kotlin. Uwe -- 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