Mailing-List: contact users-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@buildr.apache.org
Received-SPF: pass (athena.apache.org: domain of csarva@gmail.com designates
 209.85.223.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=YjtBP3jE3lvHhRQQtSy2arBkSxUFvF+moZ4wJRIQ0WvX4pmEu4nNy27eo2qWp2nh+a
         GS8EmT+03AxrUPD6aHXKGJyPKoDZP3S1DvKfZVxMCgx4QoA1IOB7eiu2w2A9S5w0gW4M
         p3IDeXUWgrhZz+kYyHMGNZQQ6DvXvjBobiLiE=
MIME-Version: 1.0
Date: Thu, 25 Feb 2010 15:33:19 -0500
Message-ID: <141c75fd1002251233s35608641x370b45cbba213e16@mail.gmail.com>
Subject: Excluding broken/missing transitive dependencies
From: Chetan Sarva <csarva@gmail.com>
To: users@buildr.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm trying to figure out how to properly exclude a transitive
dependency, particularly when one of them is broken. I've got a simple
test case:

SPRING_WEB = transitive("org.springframework:spring-web:jar:3.0.1.RELEASE").reject
{ |a| a.id == "activation" }

spring-web > jsp-api-2.1 > saaj-api-1.3 > activation-1.0.2

activation-1.0.2 is the broken dep, which I'm trying to reject but
from what I can tell, when the Artifact instance is first created it's
being added to the task chain for my project and so even though it
won't eventually get included in my projects JARs, it still does try
to download it.

Is there a workaround for this or is it a bug or new use case?

chetan