infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-3618) Apache repo are not being synced
Date Mon, 09 May 2011 13:56:03 GMT

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

Brian Demers commented on INFRA-3618:
-------------------------------------

The wink project should be deployed to repository.apache.org not people.  Mixing the deploys
will confuse the maven metadata, as it will be rsync'd from both locations.

I will move the 1.1.3-incubating release over to repository.apache.org, and rebuild the metadata.

How did you deploy this release?

> Apache repo are not being synced
> --------------------------------
>
>                 Key: INFRA-3618
>                 URL: https://issues.apache.org/jira/browse/INFRA-3618
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Luciano Resende
>            Assignee: Brian Demers
>            Priority: Blocker
>
> I have copied couple staged repos in the last couple days into 
> /www/people.apache.org/repo/m2-ibiblio-rsync-repository
> and they haven't been live yet after more then 24 or 48 hours
> Thoughts ? Ideas ?
> PS: I didn't find a repository component, so I added it as Nexus

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message