Details

    • Type: Publishing Support
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Labels:
    • Group Id:
      null
    • Publishing Hostname:
      oss.sonatype.org
    • Modify publishing permissions?:
      No

      Description

      I have a couple of artifacts in the org.basepom groupId. Those are intended to be base poms for other projects. Therefore, if they would contain any of these pieces:

      • Project name
      • Project description
      • Project URL
      • License information
      • SCM URL
      • Developer information

      and the project using the base pom(s) would not explicitly set these fields, the information would "bleed through" into the child projects, which is not intended.

      Now, the POM validation check run when a release repo should be closed fails and therefore I can not release the artifacts.

      As this behaviour is intentional and wanted, can this check please be turned off for the org.basepom groupId?

      In this specific, case it affects the orgbasepom-1021 staging repo which is still open.

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            hgschmie Henning Schmiedehausen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title