Return-Path: X-Original-To: apmail-maven-repo-maintainers-archive@minotaur.apache.org Delivered-To: apmail-maven-repo-maintainers-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A8B84966 for ; Thu, 19 May 2011 07:36:42 +0000 (UTC) Received: (qmail 14124 invoked by uid 500); 19 May 2011 07:36:42 -0000 Delivered-To: apmail-maven-repo-maintainers-archive@maven.apache.org Received: (qmail 14063 invoked by uid 500); 19 May 2011 07:36:41 -0000 Mailing-List: contact repo-maintainers-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: repo-maintainers@maven.apache.org Delivered-To: mailing list repo-maintainers@maven.apache.org Received: (qmail 14053 invoked by uid 99); 19 May 2011 07:36:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 07:36:38 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FRT_ADOBE2,HTML_MESSAGE,RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of juven@sonatype.com) Received: from [64.18.2.173] (HELO exprod7og110.obsmtp.com) (64.18.2.173) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 19 May 2011 07:36:30 +0000 Received: from mail-yi0-f47.google.com ([209.85.218.47]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTdTIaEbg+qsx2l3ymH99i3UzY6JjiGvq@postini.com; Thu, 19 May 2011 00:36:09 PDT Received: by yia13 with SMTP id 13so879833yia.6 for ; Thu, 19 May 2011 00:36:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.141.11 with SMTP id t11mr1612864ann.137.1305790565865; Thu, 19 May 2011 00:36:05 -0700 (PDT) Received: by 10.101.69.20 with HTTP; Thu, 19 May 2011 00:36:05 -0700 (PDT) In-Reply-To: <9C0FC4C8E9C29945B01766FC7F9D389816D780336C@eurmbx01.eur.adobe.com> References: <9C0FC4C8E9C29945B01766FC7F9D389816D7803369@eurmbx01.eur.adobe.com> <9C0FC4C8E9C29945B01766FC7F9D389816D780336C@eurmbx01.eur.adobe.com> Date: Thu, 19 May 2011 15:36:05 +0800 Message-ID: Subject: Re: Managing com.adobe on Maven Central From: Juven Xu To: repo-maintainers@maven.apache.org Cc: Ryan Heaton , Tom Jordahl , Damon Cooper , Joel Orlina Content-Type: multipart/alternative; boundary=0016e68e9fead458e304a39c0ec8 X-Virus-Checked: Checked by ClamAV on apache.org --0016e68e9fead458e304a39c0ec8 Content-Type: text/plain; charset=UTF-8 Hi Jukka, Welcome to Maven Central and manage the com.adobe artifacts. The easiest way to control com.adobe artifacts in central is using our OSS Repository Hosting Service [1]. So once you create a ticket, we will prepare repository for you and make sure nobody else deploy com.adobe artifacts into maven central. Regarding the currently uploaded BlazeDS artifacts in central, sorry we can't simply delete them or place a pointer to your official download page. It's because: * It will break people's build, and we have no idea how many people are using them. * These artifacts were already mirrored a lot. So, in principle we don't delete/change any file in central, unless the artifact is totally wrong. People usually need to deploy a new version if they find something wrong with their deployed artifacts. So you can deploy a new version as well. [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide On Thu, May 19, 2011 at 6:05 AM, Jukka Zitting wrote: > Hi Ryan, > > From Ryan Heaton: > > Just for the record, I'm glad that Adobe is taking this on and > > I'd be happy to relinquish my "unofficial maintainer" role. > > Great to hear that, and thanks for your work so far! > > > Why don't you guys just open up a JIRA issue explaining the request? > > I'd be happy to comment on it with my approval. > > We'll probably do that soon. I wanted to contact repo-maintainers@ first > to figure out what's the best way to proceed with this. > > Best regards, > > Jukka Zitting > > -- - Juven Xu --0016e68e9fead458e304a39c0ec8--