[
https://issues.apache.org/jira/browse/MNG-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620147#comment-16620147
]
Hervé Boutemy commented on MNG-5870:
------------------------------------
like that, why not
I'm convinced that we should not need such a difference between build and
consumer pom if maven-scm urls for DVCS were powerful enough
But at least for web view urls, having this separation between build and
consumer makes sense, even if Jenkins experience for creating a web link to scm
view is just a nightmare given the huge diversity of systems...
we really need to work on this build vs consumer POM
> Effective pom should not inherit SCM
> ------------------------------------
>
> Key: MNG-5870
> URL: https://issues.apache.org/jira/browse/MNG-5870
> Project: Maven
> Issue Type: Improvement
> Components: core, Inheritance and Interpolation, POM
> Reporter: Robert Scholte
> Priority: Major
>
> Up until Maven 3.3.7 if a pom didn't specify the scm section, it would be
> inherited and extended with the artifactId *by default*. This mechanism could
> work for a couple of SCMs like svn and cvs, but for most it doesn't.
> This kind of scm specific logic of extending the connection or URL doesn't
> belong in Maven core.
> Instead we should say that scm marks this project as a valid release root.
> The source repository page (mpir) should ask a specific Scm class for
> handling connections and urls in case of modules.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
