[
https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032140#comment-15032140
]
Michael Osipov commented on MNG-5878:
-------------------------------------
Hervé, I am somewhat confused by this solution. It looks like duplicate
information. Might there be anycase when module name != artifactId but
{{project.directory}} != module name?
> add support for module name != artifactId in every calculated URLs (SCM,
> site): special project.directory property
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-5878
> URL: https://issues.apache.org/jira/browse/MNG-5878
> Project: Maven
> Issue Type: New Feature
> Components: Inheritance and Interpolation
> Affects Versions: 3.3.3
> Reporter: Michael Osipov
> Assignee: Hervé Boutemy
> Fix For: 3.4.0
>
>
> Say you have this project structure:
> {noformat}
> /
> |-- module1
> |-- module2
> {noformat}
> and artifactIds are named:
> {noformat}
> my-parent
> |-- my-module1
> |-- my-module2
> {noformat}
> Prefix {{my-}} is omitted for brevity in module names. For instance, Jersey
> does that.
> When the SCM report is built, the artifactId is always used for path
> composition which leads to incorrect URLs. You can of course set the
> parameter {{checkoutDirectoryName}} but this would be extremely tedious for
> all modules down the tree.
> The code should obtain the module name and use it for URL composition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
