ChrisHegarty commented on pull request #470: URL: https://github.com/apache/lucene/pull/470#issuecomment-986901824
@dweiss You might well be right. One thing that is frustrating about Gradle's built-in module support is that it seems to be triggered by the presence of a module-info.java in the to-be-compiled project. What we're seeing here is that that kinda crude modular support enabled-or-not switch is not sufficient. The presence, or not, of a module-info.java in the to-be-compiled project could be viewed as a determination of whether that particular node in the graph, the root, is modular or not. Not whether to enable modular support for further nodes. 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, all child nodes in the graph should be interpreted as modules (shuffled to the module path). -- 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
