[
https://issues.apache.org/jira/browse/MPIR-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679111#comment-14679111
]
Hervé Boutemy edited comment on MPIR-312 at 8/9/15 11:53 AM:
-------------------------------------------------------------
a new idea: during build, there is already the algorithm to use local path
for artifacts from repo, perhaps we could use flatten-maven-plugin to detect
that the "module directory = artifactId" convention is not used then expand
calculated info flattened pom.xml
was (Author: hboutemy):
a new idea: during build, there is already the algorithm to use local path
for artifacts from repo, perhaps we could use flatten-maven-plugin to detect
that the "module directory = artifactId" convention is not used then expand
calculated info flattened pom.xml
> Subversion SCM module URLs incorrectly build when module name != artifactId
> ---------------------------------------------------------------------------
>
> Key: MPIR-312
> URL: https://issues.apache.org/jira/browse/MPIR-312
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.7
> Reporter: Michael Osipov
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
