Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <491618FC.3080607@ukf.net>
Date: Sat, 08 Nov 2008 22:55:56 +0000
From: Max Bowsher <maxb1@ukf.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7
MIME-Version: 1.0
To: dev@apr.apache.org
CC: =?ISO-8859-1?Q?Andr=E9_Malo?= <nd@perlig.de>,
 "Alan D. Cabrera" <list@toolazydogs.com>
Subject: Re: Apache Portable Runtime artifacts
References: <8A57D7FB-D3BB-41C7-8DF2-A1EBCA49439C@toolazydogs.com>
 <49159BB5.1050300@apache.org>
 <29051CDC-B8F7-4209-8237-AC9450D46B95@toolazydogs.com>
 <200811082301.21982@news.perlig.de>
In-Reply-To: <200811082301.21982@news.perlig.de>
OpenPGP: id=C0F2C580
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig9EB37E1518C8B5459FFB714F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9EB37E1518C8B5459FFB714F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Andr=E9 Malo wrote:
> * Alan D. Cabrera wrote:
>> On Nov 8, 2008, at 6:01 AM, Max Bowsher wrote:
>>> Alan D. Cabrera wrote:
>>>> I would like to publish the APR artifacts into the Maven repository,=

>>>> [1].  I think that the group id should be org.apache.apr and the
>>>> artifact id should be apr.
>>>>
>>>> Does anyone have a problem with these group and artifact ids?  Does
>>>> anyone have a problem with me publishing these artifacts?
>>> What are the specifics of the artifacts you were thinking of
>>> publishing?
>>> APR is not a Java project after all.  I do realize that strictly
>>> speaking, Maven is not just for Java, but any publishing of native
>>> code into Maven tends to be fraught with difficulties.
>> What difficulties are you speaking of?

The difficulty is that there is no standard on how to manage the
multitude of flavours of native binaries that are possible.

For example, there's architecture and OS that need to be considered, but
for all but then you start to get things like C library version being
involved. If you are looking to do anything with apr-util as well as apr
itself, then the problem explodes with the number of extra dependencies.

>> You are correct, I want to publish the APR libraries so that they may
>> be pulled in by  projects built with the Maven native plugin [1].
>>
>>> It would probably be best for the precise files being published to be=

>>> acked by an APR committer or PMC member before publishing.
>>> Actually, wouldn't published Maven artifacts be considered an ASF
>>> release and therefore needful of PMC voting?
>> Makes sense to me.  How, exactly, should we do this?  Should I file
>> Jiras w/ the POMs for the artifacts, [2], and then start a vote?

APR lives in Bugzilla rather than JIRA, but I'd suggest the best place
to start would be posting POMs and build recipes for the binaries to go
with them to this list.

> Doesn't make sense to me, as the ASF doesn't release binaries. Has that=
 been=20
> changed?

Lots of (Java) ASF projects provide binaries on
http://www.apache.org/dist/. I don't know whether those are semantically
considered releases or just arbitrarily distributed files that happen to
coincidentally be derived from actual releases.

Max.


--------------enig9EB37E1518C8B5459FFB714F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkWGQYACgkQfFNSmcDyxYCoVgCgrjdQ+ABHIeJiWKPyFR/QgdBM
iNwAn2Z+M4ZNl1hjcvuTfbnc4EM0vxKA
=bxfT
-----END PGP SIGNATURE-----

--------------enig9EB37E1518C8B5459FFB714F--