ascheman commented on PR #11549: URL: https://github.com/apache/maven/pull/11549#issuecomment-3653848868
> IIUC, you expect to use the same consumer pom for automatic artifactIds of Java module JAR, just update the artifactId? and implicitely no build pom? Well, the overall context is a project where you have multiple Java modules. I have provided some examples [here](https://github.com/support-and-care/java9-jigsaw-examples/). If I pick one (cf. an arbitrary [`pom.xml`](https://github.com/support-and-care/java9-jigsaw-examples/blob/main/jigsaw-examples/example_layer-hierarchy/m4/pom.xml), same holds for almost each example, cf. their m4 subdirectories), there is usually just one build POM. But the build would result in multiple binary artefacts (or it could result in such as this is work-in-progress), one for each module. For each such module JAR there must be a separate consumer POM as they can be used independently. These can be derived from the build POM. AFAIK there is no concept to explicitly provide a consumer POM for a module (and in most cases this should not be necessary as they can be derived from the build POM). > for better understanding of this plan (that would deserve more than a small discussion in an issue in Maven core: is there a doc somewhere?), is there a convention between original artifactId and automatic artifactIds? There seems not to be much documentation about M4 consumer POM concepts or a specification how to work with Java modules (I'd be happy to find more about it). That said, I'd be volunteering to create such concept documentation. > and is there a jar associated to the original artifactId? For a multi-module project there is not much need to create a binary (classes) JAR for the project itself, as each module should result in its own jar. Perhaps the sources or javadocs etc. could be created from the original project. This might be subject to discussion. -- 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]
