Return-Path: X-Original-To: apmail-archiva-dev-archive@www.apache.org Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A947DCD4 for ; Tue, 25 Sep 2012 08:46:07 +0000 (UTC) Received: (qmail 48997 invoked by uid 500); 25 Sep 2012 08:46:07 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 48955 invoked by uid 500); 25 Sep 2012 08:46:06 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 48937 invoked by uid 99); 25 Sep 2012 08:46:05 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 08:46:05 +0000 Received: from localhost (HELO mail-ie0-f170.google.com) (127.0.0.1) (smtp-auth username olamy, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2012 08:46:05 +0000 Received: by iebc12 with SMTP id c12so9856985ieb.15 for ; Tue, 25 Sep 2012 01:46:05 -0700 (PDT) Received: by 10.50.153.195 with SMTP id vi3mr7325555igb.23.1348562764995; Tue, 25 Sep 2012 01:46:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.115.215 with HTTP; Tue, 25 Sep 2012 01:45:44 -0700 (PDT) In-Reply-To: References: From: Olivier Lamy Date: Tue, 25 Sep 2012 10:45:44 +0200 Message-ID: Subject: Re: Release to central To: dev@archiva.apache.org Content-Type: text/plain; charset=ISO-8859-1 2012/9/25 Olivier Lamy : > 2012/9/25 Brett Porter : >> I think we should ask first if central will sync from archiva-repository for selected group IDs to accommodate (we are still within their forge policy). >> >> Failing that, we should rsync the content into r.a.o to be picked up, rather than deploying to nexus. That's a lot of manual double-work (and not dogfooding would not be an option). > I have to verify but stage:copy should work with https as target repository. Until it's fixed. I have merged the stage repo to https://archiva-repository.apache.org/archiva/repository/archiva-releases/ I will add this in ours poms and continue the release. I will be able later to put this content to apache nexus. BTW I'm not sure we need a central sync :-) we have a repo here https://archiva-repository.apache.org/archiva/repository/archiva-releases/ > >> >> - Brett >> >> On 25/09/2012, at 6:04 PM, Olivier Lamy wrote: >> >>> Hi, >>> It looks rsync from >>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository to maven >>> central is not anymore supported. (Don't ask me why I have some ideas >>> but I prefer to not discuss on the topic.....) >>> So if we want our release going to central we have deployed releases to nexus. >>> I will created jira entry for that. >>> >>> >>> -- >>> Olivier Lamy >>> Talend: http://coders.talend.com >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> -- >> Brett Porter >> brett@apache.org >> http://brettporter.wordpress.com/ >> http://au.linkedin.com/in/brettporter >> http://twitter.com/brettporter >> >> >> >> >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy