[
https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15039488#comment-15039488
]
Hervé Boutemy commented on MNG-5878:
------------------------------------
that's not so easy to imagine: that's why I wrote unit tests regarding url
interpolation :)
imagine: parent pom has 4 modules: module-a, module-b, module-c and module-d
and module-a has "artifact-a" artifactId
When bluiding, with module-a module in module-a directory, yes, this
project.directory is a duplication of information
But once everything is deployed to repository, and you try to calculate
effective artifact-a, you can't know which of the 4 modules it represents if it
doesn't contain a hint to tell "I'm module-a: that's the relative path to add
to parent url"
> 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)
