desruisseaux commented on PR #959: URL: https://github.com/apache/maven-compiler-plugin/pull/959#issuecomment-3405371648
Maybe we do not need to change maven#1838. We could keep the current view — each Maven sub-project generates a single main artefact — and instead see each Java module as a dynamic Maven sub-project, except that the sub-project is described by `module-info.java` instead of `pom.xml`. The reason why I'm thinking to this approach is because each Java module will need its own `artifactId` anyway for deployment on Maven Central (the `artifactId` could default to the Java module name) with its own `pom.xml` generated by intersecting the parent `pom.xml` with `module-info`. It would be consistent with the new approach in Maven 4 where the `pom.xml` used for building the project is no longer the same (or not necessarily the same) as the deployed `pom.xml`. So in short, I envision that a Maven project using Module Source Hierarchy could be seen as a parent `pom.xml` with sub-projects defined by the `module-info.java` files. It may be possible to fit this approach with the "one main artefact per sub-project" expectation. -- 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]
