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 sebbaz@gmail.com designates
 209.85.214.171 as permitted sender)
Received-SPF: pass (google.com: domain of sebbaz@gmail.com designates
 10.60.4.162 as permitted sender) client-ip=10.60.4.162;
MIME-Version: 1.0
In-Reply-To: 
 <CAOGo0Va=Uz4HKq6TYa0i+SJNwiqnQLG1c3nKj=B7N1Ce0hY=0Q@mail.gmail.com>
References: <4F46CE99.30105@apache.org>
	<4F4BB8EA.30807@apache.org>
	<CAOGo0VbRAB43KLx7Bzq1jJupAu9J9Ot4gR-QXMrR9MoG9x58zA@mail.gmail.com>
	<4F4BC417.2050400@apache.org>
	<CAOGo0Va=Uz4HKq6TYa0i+SJNwiqnQLG1c3nKj=B7N1Ce0hY=0Q@mail.gmail.com>
Date: Mon, 27 Feb 2012 23:48:07 +0000
Message-ID: 
 <CAOGo0VayePzwb_Vu+RfNFy8WhRzfLcZkikfmUWK1V34Q+URYvA@mail.gmail.com>
Subject: Re: [RESULT] Was: [VOTE] Release Apache Commons Daemon 1.0.10 based
 on RC2
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On 27 February 2012 22:45, sebb <sebbaz@gmail.com> wrote:
> On 27 February 2012 17:57, Mladen Turk <mturk@apache.org> wrote:
>> On 02/27/2012 06:14 PM, sebb wrote:
>>>
>>> Can you also release the jar to Maven please?
>>
>>
>> Sure, already did steps described at
>> http://commons.apache.org/releases/release.html
>>
>> files are already inside
>> /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/commons/commons-daemon
>> and maven-metadata.xml updated.
>>
>> According to the release.html this should sync to repo1.maven.org
>> (if the instructions are valid of course)
>
> They are out of date for Nexus-enabled components, which Daemon is.
>
> Not sure how you managed to update the directory; when a component
> uses Nexus, manual updates are supposed to be disabled.
>
> I see that the 1.0.9 jar is also present, but has not been propagated
> to Maven Central (as we know from the Clirr story).
>
> [Later]
>
> Just realised what the problem is - the files are installed under the
> directory which corresponds to the groupId org.apache.commons, but the
> pom actually has groupId commons-daemon. This is one of the pitfalls
> of the manual deployment method in the (outdated) release docs.
>
> I can probably fix that via Nexus.

Done. Should appear in Maven Central in a day or so.

> Note: we could change the groupId to o.a.c, but that would require a
> package name change as well otherwise classpath clashes could occur.
>
>>
>>
>> Regards
>> --
>> ^TM
>>
>> ---------------------------------------------------------------------
>> 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