Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (athena.apache.org: domain of gscokart@gmail.com designates
 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=VTlUy26h2DlnvcnL11Rt/Yf4YmzF48rCS3KHebiehC7N66kVucGhOTlRSiBJRd/1kK
         uLFQooVTd+VD3Rj7W/rBuLQTKB9OjgdutcBijBVWg1IojU7mbV68CxxCTo2nnbNl9MXX
         Bu3SdhzaLlZjlSfNG7o7f1xv96o0GOCZN74gU=
Message-ID: <e9d8a2610810080640t5953d42ch7e538c1b41eb3a64@mail.gmail.com>
Date: Wed, 8 Oct 2008 15:40:30 +0200
From: "Gilles Scokart" <gscokart@gmail.com>
To: ivy-user@ant.apache.org, "Ant Users List" <user@ant.apache.org>
Subject: Reinforce dependency control
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

When working on some big project with heavy history and when looking
at the quality of some meta data in the maven repository I'm always
shoked by the amount of useless dependencies used.

To counter that, I would like to use (and promote) a tool that help
the developpers to limit their path to the strict minimum.

I would like to start with the easiest : the compile path.  (Next I
would try to do the same for test classpath, and maybe for runtime
classpath)
I would like to push my build to an extreme solution.  I want to make
a build fail if some jars of the compile path are not used.

Did you know a task that do that?  Or did you know any tools that list
the jars that are required by a sources (or a compiled jars) that I
could adapt to make such a tasks?

-- 
Gilles Scokart

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org