You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/08/19 21:42:16 UTC
[jira] Created: (INFRA-2939) Nexus access for Axis2
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.
[jira] Closed: (INFRA-2939) Nexus access for Axis2
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen closed INFRA-2939.
----------------------------------
Resolution: Fixed
It works now. Thanks Brian!
> 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.
[jira] Closed: (INFRA-2939) Nexus access for Axis2
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-2939.
----------------------------
Resolution: Fixed
all set
> 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.
[jira] Reopened: (INFRA-2939) Nexus access for Axis2
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reopened INFRA-2939:
------------------------------------
Staging failed with the follow error:
[INFO] [INFO] Error deploying artifact: Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/axis2/axis2-parent/1.5.2/axis2-parent-1.5.2.pom. Return code is: 401
My settings.xml is correct (worked for the Axiom 1.2.9 release):
<servers>
<server>
<id>apache.releases.https</id>
<username>veithen</username>
<password>********</password>
</server>
<server>
<id>apache.snapshots.https</id>
<username>veithen</username>
<password>********</password>
</server>
</servers>
Also, when logging into the Nexus UI, I don't see the Axis2 staging profile listed. There is something wrong either with the staging profile or with the groups in LDAP. Can you help us to identify the problem?
> 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.
[jira] Commented: (INFRA-2939) Nexus access for Axis2
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ 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:
https://repository.apache.org/content/repositories/snapshots/org/apache/axis2/axis2-parent/1.5.2-SNAPSHOT/axis2-parent-1.5.2-SNAPSHOT.pom
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.
[jira] Commented: (INFRA-2939) Nexus access for Axis2
Posted by "Brian Demers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905014#action_12905014 ]
Brian Demers commented on INFRA-2939:
-------------------------------------
All should be well now. let me know if you still run into issues
> 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.
[jira] Commented: (INFRA-2939) Nexus access for Axis2
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905018#action_12905018 ]
Glen Daniels commented on INFRA-2939:
-------------------------------------
Thanks Brian!
I just tested snapshot deployment, which seems to work (although it's hard to confirm - why are there no visible timestamps for artifacts via the Nexus UI?). I can now also see the org.apache.axis2 staging profile. So for me anyway things look much better.
Once Andreas tests this out, we can close this.
> 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.