[
https://issues.apache.org/jira/browse/MPIR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069603#comment-17069603
]
Hudson commented on MPIR-290:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> improve git support: remove directory info (after '.git') for "git clone"
> -------------------------------------------------------------------------
>
> Key: MPIR-290
> URL: https://issues.apache.org/jira/browse/MPIR-290
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.7
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 2.8
>
>
> actually, when a multi-module project uses git as SCM, people often let Maven
> automatically calculate scm info from parent, ie add a directory named after
> the artifact id
> then MPIR displays the info directly: this leads to messages like:
> git clone https://my.git.server.com/repository.git/artifact-id
> People should have fixed scm value in the artifact pom, but it's hard to
> explain that: people tend to imagine MPIR wrote something wrong
> Hacking MPIR scm report to remove anything after '.git' would give good git
> clone instructions deducted from wrong info in pom
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
