Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <455A202E.5020505@apache.org>
Date: Tue, 14 Nov 2006 20:59:42 +0100
From: Dennis Lundberg <dennisl@apache.org>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [Digester] Maven2 POM Questions and Proposals
References: <f8b39ace0611141023q30ca2b38h365bc74597e65fec@mail.gmail.com>
In-Reply-To: <f8b39ace0611141023q30ca2b38h365bc74597e65fec@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Craig McClanahan wrote:
> I've been reviewing the pom.xml for Digester's Maven2 build, and have a
> combination of questions and proposals to make.  I want to run this by the
> list before doing anything ... I've been out of the loop on Digester for
> quite a while, so it's unreasonable to just barge back in without
> coordinating.
> 
> * The POM declares we are targeting JDK 1.3 (or later).  I
>  presume that this is still accurate?
> 
> * I'd like to update the Commons BeanUtils dependency from
>  1.6 to 1.7, to pick up the decoupling from Commons Collections
>  (removing the need to explicitly declare this as a dependency),
>  plus the bugfixes in the later release.  Any given application
>  can override this in their own application's POM, but my belief
>  is that library releases should "encourage" updates of their own
>  dependencies to the latest versions we have tested with.  (We
>  can document that we've also tested with earlier versions, if
>  desired, but Maven doesn't know how to do things like the
>  either/or dependency on BeanUtils plus Collections).
> 
> * For similar reasons, I'd like to update the Commons Logging
>  dependency to 1.1 (but we should test against 1.0.4 too).
> 
> * The currently declared dependency on xml-apis is problematic
>  for downstream users, because it leaves the scope at its
>  default setting ("compile").  If you build a webapp with Maven2,
>  for example, this causes the XML parser to be included in the
>  WEB-INF/lib directory, even though the servlet containers will
>  essentially always provide a parser for you.  I propose to change
>  this dependency to be scope "provided", which means it will be
>  on the compile classpath for Digester, but *not* included as a
>  runtime dependency.  The implication is that the webapp (or
>  standalone app) you are building will provide a JAXP parser
>  for you, if you're running on 1.3 (not an issue on 1.4 or later,
>  since JAXP is included).
> 
> * The unit tests don't currently succeed when run from Maven2.
>  I presume that's a bad thing :-), and will dig in to see what is
>  going on.
> 
> * I'm not going to worry about the site generation, reports, or the
>  assembly stuff at the moment, but I'm sure we will need to
>  address those questions before we can actually do a release.
> 
> What do you thinK?
> 
> Craig
> 

Sounds good.

Let me know if I can help out with anything Maven related.

-- 
Dennis Lundberg

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