Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of flamefew@gmail.com designates
 209.85.198.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=ILTKdL3/YbttiLzwzwpafCkpeLMmQgkqNWjCJIHNHSzu85stOljHLXugJ+ExjJ3hGl
         GNLP/10YoHyvb71c/u7o5PbU9dqXwcS77EEbF/wOJvj9oVsY8VBOMQSbY/6wRRjjqCo8
         APjgg6/kMRsBxsrdbFHGdFAs6GI6csSO7zX1M=
MIME-Version: 1.0
In-Reply-To: <B6B33DFF-574C-4080-BBB3-EED0A0BC9887@dslextreme.com>
References: <49893A64.8030105@oliver-heger.de>
	 <55afdc850902071259j1040e0dbo4229b451125f4e2@mail.gmail.com>
	 <B6B33DFF-574C-4080-BBB3-EED0A0BC9887@dslextreme.com>
Date: Sun, 8 Feb 2009 11:55:15 -0800
Message-ID: <31cc37360902081155n4047a8d1k83efa23020f10c51@mail.gmail.com>
Subject: Re: [configuration][maven] Deploying release to maven repository
From: Henri Yandell <flamefew@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

What does that mean? We would upload to their directly rather than the
ASF sync repo?

On Sat, Feb 7, 2009 at 1:08 PM, Ralph Goers <ralph.goers@dslextreme.com> wrote:
> Actually, the maven folks (of which I am one) are creating a new Nexus repo
> at https://repository.zones.apache.org.  I would suggest we focus on using
> that in the future.
>
> Ralph
>
> On Feb 7, 2009, at 12:59 PM, Niall Pemberton wrote:
>
>> On Wed, Feb 4, 2009 at 6:49 AM, Oliver Heger
>> <oliver.heger@oliver-heger.de> wrote:
>>>
>>> According to a post on the user list the latest release of
>>> [configuration]
>>> (1.6) did not make it into the maven 2 repository.
>>>
>>> When doing the release I copied the jars and the pom into the Java
>>> repository at [1] as described in section 8 of [2]. This used to work for
>>> the older releases. Is there something more required to get the artifacts
>>> deployed to the central maven 2 repository?
>>
>> I thought configuration 1.6 was an m2 release - if it was then
>> probably should have been deployed to the pao m2 repo instead:
>>
>> http://people.apache.org/repo/m2-ibiblio-rsync-repository/
>>
>> Even then though you still need to ping repository@ for the first m2
>> release since they have to add the group to be synced
>>
>> Niall
>>
>>> Thanks
>>> Oliver
>>>
>>> [1] /www/people.apache.org/repo/m1-ibiblio-rsync-repository
>>> [2] http://commons.apache.org/releases/release.html
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org