Return-Path: 
 <ivy-user-return-125-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 19788 invoked from network); 12 Dec 2006 10:18:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 12 Dec 2006 10:18:24 -0000
Received: (qmail 11044 invoked by uid 500); 12 Dec 2006 10:18:08 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 10997 invoked by uid 500); 12 Dec 2006 10:18:08 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 10972 invoked by uid 99); 12 Dec 2006 10:18:08 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 02:18:07 -0800
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of xavier.hanin@gmail.com
 designates 64.233.182.184 as permitted sender)
Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 02:17:57 -0800
Received: by nf-out-0910.google.com with SMTP id a4so195861nfc
        for <ivy-user@incubator.apache.org>;
 Tue, 12 Dec 2006 02:17:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=ZOngPANuHcDPrsV7d2qoExq6yP0r7S/L682kZeAlmjQVkCUdPrb03m/vUGXQFMXyt1DlvrN+blPOYolCL1CWsguDVje49qYJW7IaZ9pTK/O0MekkvumusZu528L0xLLHVBGlRausOUM/bYgiPZp73D7xnBlAJosMe2dFluwk+ew=
Received: by 10.82.126.5 with SMTP id y5mr633158buc.1165918653506;
        Tue, 12 Dec 2006 02:17:33 -0800 (PST)
Received: by 10.82.126.18 with HTTP; Tue, 12 Dec 2006 02:16:57 -0800 (PST)
Message-ID: <635a05060612120216h4421603fn1154305696d6ad6c@mail.gmail.com>
Date: Tue, 12 Dec 2006 11:16:57 +0100
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: pulling artifacts into classpaths
In-Reply-To: <457D8B2D.8000907@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_114679_23479880.1165918617344"
References: <4579F20E.1000108@apache.org>
	 <635a05060612100154l25009db9h9e0ea309e3c5f467@mail.gmail.com>
	 <457D8B2D.8000907@apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_114679_23479880.1165918617344
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 12/11/06, Steve Loughran <stevel@apache.org> wrote:
>
> Xavier Hanin wrote:
> > On 12/9/06, Steve Loughran <stevel@apache.org> wrote:
> >>
> >>
> >> How do I get generated artifacts into my test classpath?
> >>
> >> That is, if I associate a Jar artfact with the "master" configuration,
> >> how do I get that artifact pulled into the test config. Is it as simple
> >> as saying that the test configuration extends master?
> >>
> > Yes!
> >
>
> Well, I can't seem to get it working.
>
> I have a config file:
>
> http://svn.sourceforge.net/viewvc/smartfrog/trunk/core/components/xml/ivy.xml?view=markup
>
> it generates artifacts in the master build
>
>     <publications>
>       <artifact conf="master"/>
>     </publications>
>
> And the test conf depends on it
>
>      <conf name="test" extends="default,parser"
>           description="the classpath needed to run tests"/>
>
> Which I then pull in
> <ivy:cachepath pathid="exec.classpath" conf="test" />
>
> but I dont see the artifacts in the resulting classpath. dependents yes,
> artifact no


Ok, I misunderstood what you were asking. All resolve related tasks in Ivy
only deal with dependencies, not published artifacts. The only tasks dealing
with the publication section is publish. So if you want to use Ivy to build
path with both your dependencies and your published artifacts, you have to
first publish your module to your repository (maybe only a local one), and
then you'll be able to build a path based upon your module by using the
inline option of resolve (and cachepath also I think, don't have time to
check right now).

Xavier

      [echo] exec.classpath=/home/slo/.ivy/cache/xom/xom/jars/xom-1.1.jar:
>   home/slo/.ivy/cache/jaxen/jaxen/jars/jaxen-1.1-beta-8.jar:
> /home/slo/.ivy/cache/org.smartfrog/smartfrog/jars/smartfrog-
> 3.10.slo-private.jar:
> /home/slo/.ivy/cache/org.smartfrog/smartfrog/jars/sfServices-
> 3.10.slo-private.jar:
> /home/slo/.ivy/cache/org.smartfrog/smartfrog/jars/sfExamples-
> 3.10.slo-private.jar:
> /home/slo/.ivy/cache/xerces/xercesImpl/jars/xercesImpl-2.6.2.jar:
> /home/slo/.ivy/cache/xerces/xmlParserAPIs/jars/xmlParserAPIs-2.6.2.jar:/
> home/slo/.ivy/cache/org.smartfrog/sf-testharness/jars/sf-
> testharness-3.10.slo-private.jar:
> /home/slo/.ivy/cache/junit/junit/jars/junit-3.8.2.jar
>
> How do i get the Jar I'm building into the classpath of the test
> compile/run?
>
> -steve
>

------=_Part_114679_23479880.1165918617344--