dweiss commented on pull request #470: URL: https://github.com/apache/lucene/pull/470#issuecomment-986880672
You're right, @ChrisHegarty - I didn't consider such a scenario. A similar trick can be used to what I suggested: disable the built-in module path resolver, use a custom one... but it would indeed have to scan the dependency graph from the corresponding configuration and figure out which dependency to put where... And it may not even be consistent if a non-modular JAR is a dependency from a modular subproject A and a dependency from a non-modular subproject B... Ouch. I'm sure Lucene's setup will be easier than Elasticsearch's but it'd be great to arrive at a conclusion that fits both. -- 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
