dweiss commented on pull request #470: URL: https://github.com/apache/lucene/pull/470#issuecomment-988215171
I went back to explicit configurations for modular dependencies. Maybe it doesn't fit the gradle convention model but it's simpler and less magical in the end (no automatic detections, just separation of paths and dependency trees). The next logical steps would be, to me, trying to compile tests the same way (adding module-based test configurations) so that you can have a proper test module depending on, say, org.apache.lucene.core. After that: running tests using module path (as modules). I'll try to tackle compilation first, then proceed to tests - @mocobeta your PR will no longer compile but leave it in, I'm sure we can convert that to a module-based test at some point. -- 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
