Return-Path: 
 <commons-dev-return-89161-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 449 invoked from network); 15 May 2006 21:22:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 15 May 2006 21:22:14 -0000
Received: (qmail 20784 invoked by uid 500); 15 May 2006 21:22:01 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 20700 invoked by uid 500); 15 May 2006 21:22:01 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 20652 invoked by uid 99); 15 May 2006 21:22:01 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2006 14:22:01 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of carlossg@gmail.com designates
 64.233.184.233 as permitted sender)
Received: from [64.233.184.233] (HELO wr-out-0506.google.com) (64.233.184.233)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2006 14:21:59 -0700
Received: by wr-out-0506.google.com with SMTP id 58so54073wri
        for <commons-dev@jakarta.apache.org>;
 Mon, 15 May 2006 14:21:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=CbrB0FIjkc0fbEzt4xeMBAzx6kDv164TK1cd/lZFWsJHm18vnQ8JGge5Rmt+rdyfc+wftX3c6uBEfr0T6OMzVnxEIPnENTfQqhJLSJDy4dhumUSWSShSq8Smt7ZuMuYGuGa3zgLb3vM56Siuq9Qs0+sOn6eP/9Xgm8R7q1IuChU=
Received: by 10.65.206.2 with SMTP id i2mr4401480qbq;
        Mon, 15 May 2006 14:21:38 -0700 (PDT)
Received: by 10.65.192.16 with HTTP; Mon, 15 May 2006 14:21:38 -0700 (PDT)
Message-ID: <1a5b6c410605151421m565f4489l92722ebdffcc027e@mail.gmail.com>
Date: Mon, 15 May 2006 14:21:38 -0700
From: "Carlos Sanchez" <carlos@apache.org>
Sender: carlossg@gmail.com
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [logging] Maven 2 POM(s) for commons-logging [Was: RE :
 [ANNOUNCEMENT] Apache Jakarta Commons Logging 1.1 Released]
In-Reply-To: <1147723866.6374.16.camel@knossos.elmet>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <001c01c677f2$80209dd0$cad9c839@eu.accor.net>
	 <4468CDCC.8060709@apache.org> <1147723866.6374.16.camel@knossos.elmet>
X-Google-Sender-Auth: 5215936e2c864d0a
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

I'm gonna tweak the poms in the repository outside of apache, please
add the optional property in the optional dependencies for future
versions.

I'll take a look to the other jars to make poms.

On 5/15/06, robert burrell donkin <robertburrelldonkin@blueyonder.co.uk> wr=
ote:
> On Mon, 2006-05-15 at 20:51 +0200, Dennis Lundberg wrote:
> > Olivier Lamy wrote:
> > > Hi,n
> > > Thanks it's great job which fixes some troubles.
> > > But I have a trouble concerning the pom published [1].
> > > I have recorded an MEV issue [2]
> > > A commons-logging developper's can put a comment or approve it ?
> > >
> > > Thanks,
> > > - Olivier
> > >
> > > [1]
> > > http://www.ibiblio.org/maven2/commons-logging/commons-logging/1.1/com=
mons-logging-1.1.pom
> > > [2] http://jira.codehaus.org/browse/MEV-392
> >
> > <snip/>
> >
> > I have written a comment in the JIRA issue about why the situation is
> > the way it is.
>
> looks good :-)
>
> > The question is how we should proceed? Should we try to
> > tweak the POM that is currently deployed [1]
>
> i didn't deploy that POM and don't have karma: we'd need to talk the to
> maven team.
>
> it's too late for me to change the release POM deployed to the Apache
> repository: it's cut. the easiest approach would be for one of the maven
> team (who has karma) to apply appropriate modifications to the POM
> version in the maven 2 repository.
>
> > or should we try to create a POM for commons-logging-api or perhaps bot=
h?
>
> not sure
>
> the API works best as a virtual dependency. it can be satisfied by JCL
> 1.0.x, 1.1.x, by ceki's adapter or by Torsten's null implementation. not
> sure whether maven 2 handles this ATM.
>
> but the API jar contains more than is necessary for this purpose.
> probably carlos is right that all the dependencies need to be marked as
> optional but the full JCL jar shipped.
>
> not sure...
>
> - robert
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>


--=20
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

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