Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5870

Effective pom should not inherit SCM

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Core, Inheritance and Interpolation, POM
    • None

    Description

      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.

      Attachments

        Issue Links

          is superceded by

          Improvement - An improvement or enhancement to an existing feature or task. MNG-5951 add an option to avoid path addition to inherited URLs

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MPIR-234 SCM-link in site of multimodule projects should not append module name by default (at least for git)

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rfscholte Robert Scholte
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: