[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698864#comment-14698864
]
Chris Graham edited comment on MPIR-234 at 8/16/15 10:53 PM:
-------------------------------------------------------------
You'd have hoped so! However, I've seen people do exactly that. Jnr devs with
little to no experience with Maven, and thus don't know about or undestand the
conventions and/or limitations of their SCM and/or maven itself.
That aside, yes, I can see how that could be an issue. Especially when module
name != artifactId. Which is something that I've always enforced (and probably
why I've never had issues such as this).
So, given that Maven is opinionware, would this not be a good time to add a few
more? That is, module name = sub dir name = artifactId? Add some enforcer rules
if need be? This would address some of the concerns above. Would it not?
was (Author: chrisgwarp):
You'd have hoped so! However, I've seen people do exactly that. Jnr devs with
little to no experience with Maven, and thus don't know about or undestand the
conventions and/or limitations of their SCM and/or maven itself.
That aside, yes, I can see how that could be an issue. Especially when module
name != artifactId. Which is something that I've always enforced (and probably
why I've never had issues such as this).
So, given that Maven is opinionware, would this not be a good time to add a few
more? That is, module name = sub dir name = artifactId? Add some enforced rules
if need be? This would address some of the concerns above. Would it not?
> 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/,
> [email protected]: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)