ascheman commented on PR #11549: URL: https://github.com/apache/maven/pull/11549#issuecomment-3655116297
> * Since Java 9, `javac` can compile many modules at once. This is possible when using the so-called [module source hierarchy](https://docs.oracle.com/en/java/javase/25/docs/specs/man/javac.html#directory-hierarchies). > * There are some [technical advantages](https://sis.apache.org/release-notes/Modularization.html#advantages) in doing that, and no way I'm aware of to get some of these advantages in the traditional way. > * When using module hierarchy, the `javac` output is `<module>/<package>/*.class`. The `<module>` additional level is a standard Java output, not something that we decided on our side. > * The above additional `<module>` directory level is understood by other standard Java tools such as `java` and `javadoc`. One notable exception is the `jar` tool, maybe intentionally for forcing a limitation of one module per JAR for smaller download. > > They are been attempts to explain these aspects on the Maven mailing list, on [a wiki with proof of concept](https://github.com/Geomatys/maven/wiki) and with a [real project experiment using Gradle](https://sis.apache.org/release-notes/Modularization.html). However, I got the feeling that the above is still nebulous to most peoples, and that the best way to advance would be to give to developers a possibility to try easily by themselves. Would you mind if we add a respective (sub-) page to the Confluence as documentation of this background to Java modules? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
