maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] (MPIR-290) improve git support: remove directory info (after '.git') for "git clone"
Date Tue, 10 Sep 2013 22:06:52 GMT

     [ https://jira.codehaus.org/browse/MPIR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herve Boutemy closed MPIR-290.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.8
         Assignee: Herve Boutemy

done in [r1521663|http://svn.apache.org/r1521663]
                
> improve git support: remove directory info (after '.git') for "git clone"
> -------------------------------------------------------------------------
>
>                 Key: MPIR-290
>                 URL: https://jira.codehaus.org/browse/MPIR-290
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.7
>            Reporter: Herve Boutemy
>            Assignee: Herve 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message