www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2939) Nexus access for Axis2
Date Sun, 29 Aug 2010 13:44:53 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903969#action_12903969

Glen Daniels commented on INFRA-2939:

I don't see the staging profile either - I assume anyone in the Axis LDAP group should be
able to see it?

I also tried deploying a snapshot yesterday and got an "access denied" error:

[INFO] Error deploying artifact: Authorization failed: Access denied to:

I'm a Nexus-newbie, but this leads me to wonder if the problem might have to do with the LDAP
setup for the project repo?

> Nexus access for Axis2
> ----------------------
>                 Key: INFRA-2939
>                 URL: https://issues.apache.org/jira/browse/INFRA-2939
>             Project: Infrastructure
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Andreas Veithen
>            Assignee: Brian Fox
> The Apache Axis2 project (subproject of the Apache Axis TLP) would like to use Nexus
to stage releases.
> The group ID of Axis2 is org.apache.axis2. We have a committer = PMC member policy, so
that there is no need to define different roles for staging and promoting releases.
> Note that some time ago I asked the other subprojects (such as Rampart) if we should
migrate all subprojects simultaneously and include their groupIds in the staging profile,
but I didn't get any answer. Therefore, the groupId filter should be limited to org.apache.axis2.
This will include the Axis2 core project (which is currently preparing the next release) and
the Axis2 Transports project (which I will take care of). The other projects will continue
to use the old release process or request migration later.
> Thanks in advance. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message