[
https://issues.apache.org/jira/browse/MPIR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679299#comment-14679299
]
Hudson commented on MPIR-290:
-----------------------------
FAILURE: Integrated in maven-3.x #1101 (See
[https://builds.apache.org/job/maven-3.x/1101/])
removed unused config since MPIR is at 2.8 with MPIR-290 (hboutemy: rev
d25669e0bb82a8702604a57daaefd526fd964938)
* maven-artifact/pom.xml
* maven-embedder/pom.xml
* maven-aether-provider/pom.xml
* maven-plugin-api/pom.xml
* maven-settings/pom.xml
* apache-maven/pom.xml
* maven-settings-builder/pom.xml
* maven-model-builder/pom.xml
* maven-model/pom.xml
* maven-core/pom.xml
* maven-builder-support/pom.xml
* maven-repository-metadata/pom.xml
* maven-compat/pom.xml
> 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: Hervé Boutemy
> Assignee: Hervé Boutemy
> 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
(v6.3.4#6332)
