Re: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

Le 24/02/2012 00:41, Mladen Turk a écrit :

> Fixed a typo in RC1 which caused compile failure in case there
> were no sys/capability.h header on the system.
> The new set of artefacts [1] and site [2] are at usual place
> based on tag [3]
>
>
> Please vote (vote will remain open for at least 72 hours).
>
> Apache Commons Daemon 1.0.10 is
> [X] +1 Release

Re: [VOTE] Release Apache Commons Daemon 1.0.10 based on RC2

On 02/25/2012 07:50 PM, Gary Gregory wrote:
> On Fri, Feb 24, 2012 at 12:15 PM, sebb<[hidden email]> wrote:
>>
>> I've discovered the problem - Daemon 1.0.9 has not been deployed to
>> Maven Central.
>>
>
> So... don't we need to do that /now/ so we can see what Clirr says when you
> download and run a src package?
>

It won't say anything. Complete waste of time IMHO.
The change is in one .c file, and clirr has no clue about that.

On 27 February 2012 17:10, Mladen Turk <[hidden email]> wrote:
> With required 3 binding +1's from Luc, Jörg and I
> and one -0 from Garry I declare this vote as passed.
> Will copy the artefacts to dist site and make ANN tomorrow
> after the mirrors pick up.

> 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.

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.

> On 27 February 2012 17:57, Mladen Turk <[hidden email]> 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.

> On 27 February 2012 17:57, Mladen Turk<[hidden email]> wrote:
>>
>> 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.
>