Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Sun, 9 Aug 2015 11:53:46 +0000 (UTC)
From: =?utf-8?Q?Herv=C3=A9_Boutemy_=28JIRA=29?= <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12805457.1417076352000.15708.1439121226541@Atlassian.JIRA>
In-Reply-To: <JIRA.12805457.1417076352000@Atlassian.JIRA>
References: <JIRA.12805457.1417076352000@Atlassian.JIRA>
 <JIRA.12805457.1417076352169@arcas>
Subject: [jira] [Comment Edited] (MPIR-312) Subversion SCM module URLs
 incorrectly build when module name != artifactId
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MPIR-312?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D146791=
11#comment-14679111 ]=20

Herv=C3=A9 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 detec=
t that the "module directory =3D artifactId" convention is not used then ex=
pand 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 detec=
t that the "module directory =3D artifactId" convention is not used then ex=
pand calculated info flattened pom.xml

> Subversion SCM module URLs incorrectly build when module name !=3D artifa=
ctId
> -------------------------------------------------------------------------=
--
>
>                 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, Jers=
ey does that.
> When the SCM report is built, the artifactId is always used for path comp=
osition which leads to incorrect URLs. You can of course set the parameter =
{{checkoutDirectoryName}} but this would be extremely tedious for all modul=
es 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)