Uploaded image for project: 'Community Support - Open Source Project Repository Hosting'
  1. Community Support - Open Source Project Repository Hosting
  2. OSSRH-50614

Staging profile configuration for jakarta.enterprise:jakarta.enterprise.cdi-api

    XMLWordPrintable

    Details

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

      Description

      We have two Jenkins release jobs for the cdi-bot user that should both be using an eclipse jakarta staging repository similar to the rest of the Eclipse Jakarta ee4j projects. However, the release job for the jakarta.enterprise:jakarta.enterprise.cdi-api is using a central bundles repo like:

      https://oss.sonatype.org/service/local/staging/deployByRepositoryId/central_bundles-18501

       

      The jakarta.inject:jakarta.inject-api release job run with the same configuration of the nexus:staging plugin places the staging artifacts in a repo like:

      https://oss.sonatype.org/content/repositories/jakartainject-1001

       

      When I looked at the debug output from the staging phase, the  jakarta.enterprise:jakarta.enterprise.cdi-api job shows a stagingProfiles configuration like:

        

       

      <stagingProfiles>
        <data>
          <stagingProfile>
            <resourceURI>https://oss.sonatype.org/service/local/staging/profile_evaluate/7edbe315063867</resourceURI>
            <id>7edbe315063867</id>
            <name>Central Bundles</name>
            <repositoryTemplateId>default_hosted_release</repositoryTemplateId>
            <repositoryType>maven2</repositoryType>
            <repositoryTargetId>1</repositoryTargetId>
            <inProgress>false</inProgress>
            <order>32129</order>
            <deployURI>https://oss.sonatype.org/service/local/staging/deploy/maven2</deployURI>
            <targetGroups>
              <string>central-staging</string>
            </targetGroups>
            <finishNotifyRoles/>
            <promotionNotifyRoles/>
            <dropNotifyRoles/>
            <finishNotifyEmails>central@sonatype.com</finishNotifyEmails>
            <promotionNotifyEmails>central@sonatype.com</promotionNotifyEmails>
            <dropNotifyEmails>central@sonatype.com</dropNotifyEmails>
            <closeRuleSets>
              <string>5e9e8e6f8d20a3</string>
            </closeRuleSets>
            <promoteRuleSets/>
            <promotionTargetRepository>central-sync</promotionTargetRepository>
            <mode>BOTH</mode>
            <finishNotifyCreator>false</finishNotifyCreator>
            <promotionNotifyCreator>false</promotionNotifyCreator>
            <dropNotifyCreator>false</dropNotifyCreator>
            <autoStagingDisabled>false</autoStagingDisabled>
            <repositoriesSearchable>true</repositoriesSearchable>
            <properties class="linked-hash-map"/>
          </stagingProfile>
        </data>
      </stagingProfiles>
      

       

       

      while the jakarta.inject:jakarta.inject-api shows:

       

       

       

      <stagingProfiles>
        <data>
          <stagingProfile>
            <resourceURI>https://oss.sonatype.org/service/local/staging/profile_evaluate/cb8d53ea665cf9</resourceURI>
            <id>cb8d53ea665cf9</id>
            <name>jakarta.inject</name>
            <repositoryTemplateId>default_hosted_release</repositoryTemplateId>
            <repositoryType>maven2</repositoryType>
            <repositoryTargetId>cb8d01e5dacf7a</repositoryTargetId>
            <inProgress>false</inProgress>
            <order>32007</order>
            <deployURI>https://oss.sonatype.org/service/local/staging/deploy/maven2</deployURI>
            <targetGroups>
              <string>staging</string>
            </targetGroups>
            <finishNotifyRoles/>
            <promotionNotifyRoles/>
            <dropNotifyRoles/>
            <closeRuleSets>
              <string>5e9e8e6f8d20a3</string>
            </closeRuleSets>
            <promoteRuleSets/>
            <promotionTargetRepository>releases</promotionTargetRepository>
            <mode>BOTH</mode>
            <finishNotifyCreator>true</finishNotifyCreator>
            <promotionNotifyCreator>true</promotionNotifyCreator>
            <dropNotifyCreator>true</dropNotifyCreator>
            <autoStagingDisabled>false</autoStagingDisabled>
            <repositoriesSearchable>true</repositoriesSearchable>
            <properties class="linked-hash-map"/>
          </stagingProfile>
        </data>
      </stagingProfiles>
       
      

        

      Can you look into why this is setup this way and reconfigure jakarta.enterprise:jakarta.enterprise.cdi-api to have the same staging repository configuration as jakarta.inject:jakarta.inject-api?

       

      I had raised this issue with the Eclipse webmaster here:

      https://bugs.eclipse.org/bugs/show_bug.cgi?id=549700

      and they redirected me to here.

       

      Thanks.

       

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            starksm64 Scott M Stark
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title