jira-importer commented on issue #1030: URL: https://github.com/apache/maven-scm/issues/1030#issuecomment-2964639964
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented FYI, I'm working on better documenting this convention (see https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=33de19713387e37bd371465e52278aedd5ad0ffd ) and preparing for future enhancements (whatever they may be): see MNG-5871 I understand that "multi module function of maven the pom parent pom is orthogonal to module parent": but the algorithm for extrapolating child value from parent value is the same, since there is only one inheritance. And adding ${project.artifactId} in a parent pom will cause issues when used in child of a child, since the result won't be what you expect: the issue is not caused by inheritance but parameter interpolation that happens at the end, then the value is always the value of the current pom (see https://stackoverflow.com/questions/20513744/project-artifactid-in-parent-pom-xml-resolves-odd/20517630#20517630 ) this will probably take some time to make everybody ok on a solution (and make sure everybody understands impacts of any change): but we are going forward, we just need to stay patient and continue positive discussions -- 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]
