dweiss commented on pull request #470: URL: https://github.com/apache/lucene/pull/470#issuecomment-986909873
> If I interpret your comment above correctly, then when walking the dependency graph once a module-info.java, or module-info.class in a project is encountered, that node and all child nodes in the graph should be interpreted as modules (shuffled to the module path). I think so? I really have very little experience with modular applications but your comment makes me think this would be the case. Gradle's built-in model doesn't fit this model at all. -- 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
