Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of davidcorley@gmail.com
 designates 209.85.198.251 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=u3TTO4REXRGpUAU3k1cvX5n/a1iajyUqCr0alJkccpOrG8QY8DO5GA6OPNzXopt3bC
         wIaWkmqynI3Bg11rci0siu9l8ZmvYM3mOEjbgPeFbgNhx2KDqlVPIfCmzKbd8rRoH5G4
         d7sytPyaPsgyXWMuPWfDifSLcimPDxQ9+SIWk=
Message-ID: <26c776bf0806200208q48e564bvaf41dbe9ffb86104@mail.gmail.com>
Date: Fri, 20 Jun 2008 10:08:37 +0100
From: Dave <davidcorley@gmail.com>
To: ivy-user@ant.apache.org
Subject: Re: <ivy:cachepath> conf attribute is required but docs say it is not
 + other docs issue
In-Reply-To: <26c776bf0806200128g6562225yf18d6dc9ad93a7aa@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7731_600053.1213952917052"
References: <717428.57470.qm@web30804.mail.mud.yahoo.com>
	 <26c776bf0806200128g6562225yf18d6dc9ad93a7aa@mail.gmail.com>

------=_Part_7731_600053.1213952917052
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hey Maarten,
Issues created here:
https://issues.apache.org/jira/browse/IVY-845

https://issues.apache.org/jira/browse/IVY-846

Regards,
Dave

On Fri, Jun 20, 2008 at 9:28 AM, Dave <davidcorley@gmail.com> wrote:

> No problem Maarten. I'll post back here once I have the issue numbers.
>
>
> On Thu, Jun 19, 2008 at 11:03 PM, Maarten Coene <maarten_coene@yahoo.com>
> wrote:
>
>> Dave,
>>
>> could you create a JIRA issue for your problem with ivy:cachepath?
>> I think the doc is correct in this case and should default to "*".
>>
>> Could you create another JIRA issue to document this keep attribute?
>> This attribute means that the results of the resolve are kept in memory,
>> so you can reuse it for another post-resolve task.
>>
>>
>> Maarten
>>
>>
>> ----- Original Message ----
>> From: Dave <davidcorley@gmail.com>
>> To: ivy-user@ant.apache.org
>> Sent: Thursday, June 19, 2008 6:11:07 PM
>> Subject: <ivy:cachepath> conf attribute is required but docs say it is not
>> + other docs issue
>>
>> Currently if I use the <ivy:cachepath> task without carrying out a
>> <ivy:resolve> beforehand and without setting the "conf" attribute, I see
>> the
>> following:
>> ==================
>> no conf provided for ivy cache task: It can either be set explicitely via
>> the attribute 'conf' or via 'ivy.resolved.configurations' property or a
>> prior call to <resolve/>
>> ==================
>>
>> The documentation says that Ivy should default to using the "*"
>> configuration if the conf attribute is not set. I should note I'm using
>> "inline=true" in the <ivy:cachepath> task.
>>
>> So are the docs wrong, or am I doing something wrong?
>>
>> Also, while I'm here, can I ask what the following means from the docs
>> page
>> on post-resolve tasks:
>> ==================
>> *All these tasks will trigger automatically a resolve if: *
>>
>>   - *none has already been called in the current build with the attribute
>> keep
>>   set to true (see below)*
>>
>> ==================
>>
>> There is no mention of a "keep" attribute in the <ivy:resolve> doc page,
>> so
>> what does it mean?
>>
>>
>> I use the trunk versions of Ivy, so the documentation is all up-to-date.
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> There are 10 types of people in the world.
>> Those who understand binary and those who do not.
>>
>>
>>
>>
>>
>
>
> --
> There are 10 types of people in the world.
> Those who understand binary and those who do not.
>


-- 
There are 10 types of people in the world.
Those who understand binary and those who do not.

------=_Part_7731_600053.1213952917052--