You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2017/02/23 15:01:01 UTC
[jira] [Updated] (MNG-5878) add support for module name !=
artifactId in every calculated URLs (project, SCM, site): special
project.directory property
[ https://issues.apache.org/jira/browse/MNG-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MNG-5878:
----------------------------------
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> add support for module name != artifactId in every calculated URLs (project, 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.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> 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.15#6346)