jira-importer commented on issue #1030: URL: https://github.com/apache/maven-scm/issues/1030#issuecomment-2964639963
**[Rami Ojares](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rojares)** commented First of all even if I would use multi module function of maven the pom parent pom is orthogonal to module parent. What I mean with this fancy word is that choosing the parent pom is independent of choosing the module hierarchy. Go read any maven book and that's what they tell you. You could inherit the pom from your module parent but not necessarily. Secondly you don't have to organize your module hierarchy so that modules are always directly under the parent module. I remember reading about a flat hierarchy where they are siblings. Finally I am not asking a change that would break backward compatibility. I am not asking that adding the artifactId would be removed completely. I am merely asking that this undocumented and unexpected convention could be circumvented somehow. -- 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]
