[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187190#action_187190
 ] 

Brian Fox commented on MAVENUPLOAD-2560:
----------------------------------------

It separates snapshots and releases into two repos, removes the metadata and 
then Nexus can rebuild them. You need to stop users from deploying any 
snapshots to this repo, otherwise the metadata will be garbage and we can't 
sync it.

> Synchronizing the org.jvnet repository to central
> -------------------------------------------------
>
>                 Key: MAVENUPLOAD-2560
>                 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2560
>             Project: Maven Upload Requests
>          Issue Type: Wish
>            Reporter: Kohsuke Kawaguchi
>            Assignee: Brian Fox
>
> The CSV entry for the sync:
> {noformat}
> "org.jvnet","rsync://maven.hudson-ci.org/maven.org.jvnet","rsync","Kohsuke 
> Kawaguchi","[email protected]",,
> {noformat}
> The proof of the ownership of the domain can be confirmed by verifying that 
> jvnet.org belongs to java.net (more specifically Sun Microsystems --- 
> http://www.whois.net/whois/jvnet.org). I couldn't find an authoritative 
> document saying that this belongs to java.net, but as a java.net community 
> leader, I can vouch for that. You can also see a number of existing java.net 
> projects that publish in this group ID ( http://maven.dyndns.org/2/org/jvnet/ 
> )
> I'm requesting this as an administrator of java.net Maven2 repository, and 
> you can find my ID (super_kohsuke) in https://maven2-repository.dev.java.net/
> I also wanted to mention that this groupId shadows MAVENUPLOAD-2515. I 
> currently set up my rsync daemon not to serve org.jvnet.hudson from 
> rsync://maven.hudson-ci.org/maven.org.jvnet , but if it's easier for you 
> guys, I'm happy to have "org.jvnet.hudson" sync removed, and sync it through 
> this channel instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to