[ https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697360#comment-14697360 ]
Hervé Boutemy commented on MPIR-234: ------------------------------------ bq. NIT: those checkout instructions do not checkout the branch that the report was generated from if already did that in MPIR-291, available in MPIR 2.8 the only mising part is that, in MPIR-290, I don't display {{cd maven-surefire/surefire-api}} > SCM-link in site of multimodule projects should not append module name by > default (at least for git) > ---------------------------------------------------------------------------------------------------- > > Key: MPIR-234 > URL: https://issues.apache.org/jira/browse/MPIR-234 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: scm > Affects Versions: 2.4 > Reporter: Mirko Friedenhagen > > I have setup a simple multi module project (see > https://github.com/mfriedenhagen/multi-module-sample/tree/multi-site-complex) > which uses git on github as {{scm}}. While rendering the site, MPIR will by > default add the name of the module to the SCM-URLs in source-repository.html. > So instead of https://github.com/mfriedenhagen/multi-module-sample/ I see > https://github.com/mfriedenhagen/multi-module-sample/core/, > g...@github.com:mfriedenhagen/multi-module-sample.git/core and > git://github.com/mfriedenhagen/multi-module-sample.git/core in the report for > the core module. All these URLs are invalid. For SVN this could be assumed to > be the right behaviour, for git and probably other SCMs this is not true. As > a workaround I have to reconfigure the scm section (see > https://github.com/mfriedenhagen/multi-module-sample/blob/multi-site-complex/core/pom.xml) > in the modules like this: > {code:xml} > <scm> > <connection>${project.parent.scm.connection}</connection> > > <developerConnection>${project.parent.scm.developerConnection}</developerConnection> > <url>${project.parent.scm.url}</url> > </scm> > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)