dweiss commented on issue #13698: URL: https://github.com/apache/lucene/issues/13698#issuecomment-2318015631
So... it's hell again. I can't explain it but objects stored in project.ext during configuration phase seem to be dynamically changing. For example, we store testOptions as an array and append various options to this array. But after the upgrade, the array object seems to be dynamically restored for some tasks (and is incomplete). I think it has to do with "configuration cache" and how gradle actively tries to detect changes to certain objects [1]. The problem is that we actively utilize almost everything they now forbid or deprecated... I understand the wish to not execute any code during configuration but at the same time the "supported" way of doing certain things is just plain ugly, more verbose and less intuitive... Eh. I'm not sure how to proceed here yet. Seems like making it work will require a lot of adaptation to those new conventions and build code rewriting. [1] https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:troubleshooting -- 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...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
