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/10/14 01:45:48 UTC
[jira] Created: (INFRA-3068) Enable Nexus Access For commons-daemon
Enable Nexus Access For commons-daemon
--------------------------------------
Key: INFRA-3068
URL: https://issues.apache.org/jira/browse/INFRA-3068
Project: Infrastructure
Issue Type: Task
Components: Nexus
Reporter: Brian Fox
Assignee: Brian Fox
Priority: Blocker
Commons-daemon 1.0.1 was in central by an apparent manual upload and I found that 1.0.3 was in the old repo on people but Central was never configured to pick up this groupId. I went ahead and processed those artifacts over to Nexus and added commons-daemon to the existing commons role. Any future releases can now be done against the new repo and the artifacts will be picked up by Central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3068) Enable Nexus Access For commons-daemon
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-3068.
----------------------------
Resolution: Fixed
Fixed, it should be synced today. The problem goes back to the groupId. It was set to only pick up org.apache.* to make the rsync run faster. That's why we are trying to get projects to update the coordinates. hint hint.
> Enable Nexus Access For commons-daemon
> --------------------------------------
>
> Key: INFRA-3068
> URL: https://issues.apache.org/jira/browse/INFRA-3068
> Project: Infrastructure
> Issue Type: Task
> Components: Nexus
> Reporter: Brian Fox
> Assignee: Brian Fox
> Priority: Blocker
>
> Commons-daemon 1.0.1 was in central by an apparent manual upload and I found that 1.0.3 was in the old repo on people but Central was never configured to pick up this groupId. I went ahead and processed those artifacts over to Nexus and added commons-daemon to the existing commons role. Any future releases can now be done against the new repo and the artifacts will be picked up by Central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3068) Enable Nexus Access For
commons-daemon
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922082#action_12922082 ]
Niall Pemberton commented on INFRA-3068:
----------------------------------------
Hi Brian, thanks for doing this. I put 1.0.3 in http://people.apache.org/repo/m2-ibiblio-rsync-repository/commons-daemon/ - sounds like just before you picked them up and put them into Nexus. I don't see them in central yet - is there something else we need to do?
> Enable Nexus Access For commons-daemon
> --------------------------------------
>
> Key: INFRA-3068
> URL: https://issues.apache.org/jira/browse/INFRA-3068
> Project: Infrastructure
> Issue Type: Task
> Components: Nexus
> Reporter: Brian Fox
> Assignee: Brian Fox
> Priority: Blocker
>
> Commons-daemon 1.0.1 was in central by an apparent manual upload and I found that 1.0.3 was in the old repo on people but Central was never configured to pick up this groupId. I went ahead and processed those artifacts over to Nexus and added commons-daemon to the existing commons role. Any future releases can now be done against the new repo and the artifacts will be picked up by Central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3068) Enable Nexus Access For commons-daemon
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-3068.
----------------------------
Resolution: Fixed
> Enable Nexus Access For commons-daemon
> --------------------------------------
>
> Key: INFRA-3068
> URL: https://issues.apache.org/jira/browse/INFRA-3068
> Project: Infrastructure
> Issue Type: Task
> Components: Nexus
> Reporter: Brian Fox
> Assignee: Brian Fox
> Priority: Blocker
>
> Commons-daemon 1.0.1 was in central by an apparent manual upload and I found that 1.0.3 was in the old repo on people but Central was never configured to pick up this groupId. I went ahead and processed those artifacts over to Nexus and added commons-daemon to the existing commons role. Any future releases can now be done against the new repo and the artifacts will be picked up by Central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (INFRA-3068) Enable Nexus Access For
commons-daemon
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reopened INFRA-3068:
------------------------------
No they should get there automatically. I'll find out what's happening.
> Enable Nexus Access For commons-daemon
> --------------------------------------
>
> Key: INFRA-3068
> URL: https://issues.apache.org/jira/browse/INFRA-3068
> Project: Infrastructure
> Issue Type: Task
> Components: Nexus
> Reporter: Brian Fox
> Assignee: Brian Fox
> Priority: Blocker
>
> Commons-daemon 1.0.1 was in central by an apparent manual upload and I found that 1.0.3 was in the old repo on people but Central was never configured to pick up this groupId. I went ahead and processed those artifacts over to Nexus and added commons-daemon to the existing commons role. Any future releases can now be done against the new repo and the artifacts will be picked up by Central.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.