You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Brian Fox (JIRA)" <ji...@apache.org> on 2010/07/06 08:57:54 UTC

[jira] Closed: (INFRA-2848) Nexus access for Axiom

     [ https://issues.apache.org/jira/browse/INFRA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed INFRA-2848.
----------------------------

    Resolution: Fixed

All set. The reason what I can't just allow deploys for all of org.apache.ws is that not everything has been migrated from the old repo. Each time a new groupId is requested, I not only have to allow it in Nexus, but check and migrate the data from the old repo.

If your project wants everything remaining moved, that would be ideal since I could do it all in one shot instead of piecemeal.

> Nexus access for Axiom
> ----------------------
>
>                 Key: INFRA-2848
>                 URL: https://issues.apache.org/jira/browse/INFRA-2848
>             Project: Infrastructure
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Andreas Veithen
>            Assignee: Brian Fox
>
> The Apache Axiom project (subproject of WS-Commons belonging to the Apache Web Services TLP) would like to use Nexus to stage releases. The existing org.apache.ws staging profile doesn't seem to work for Axiom.
> The group ID of Axiom is org.apache.ws.commons.axiom. All committers of the WS project (LDAP group "ws") should be allowed to stage releases and PMC members should be allowed to promote releases.
> Thanks in advance.

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