Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=utimrm3999gHzCRm8o0kAOzGgo1UdbqfUylK/cYYFsmcWK+rSjo7KB9YtUGAxZuemxR2FyLBZJGxtQuEb93WZWOxJa3h51XAls2i34A8ID/7YuE9NfpO/SKG30VhikS6023nkNZuuZTYoRYbjPCrrr42QHFeeA4p8O9SmLHQkqI=;
References: 
 <OF81A34B86.35B8974F-ON80257535.004F2F97-80257535.004F53E8@targetgroup.net>
  <496254F8.302@writingshow.com>
 <3bc8237c0901051049q920a89td9feefa5592cb6e0@mail.gmail.com>
Date: Tue, 6 Jan 2009 12:43:34 -0800 (PST)
From: Maarten Coene <maarten_coene@yahoo.com>
Subject: Re: how to put the artifacts in ant classpath?
To: ivy-user@ant.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <53865.19021.qm@web30802.mail.mud.yahoo.com>

I've updated the comment on the ivy:cachepath documentation.
http://svn.apache.org/viewvc/ant/ivy/core/branches/2.0.0/doc/use/cachepath.html?view=diff&r1=732104&r2=732105&pathrev=732105

It will be online when 2.0 final is released.

Thanks for the feedback.
Maarten


----- Original Message ----
From: Archie Cobbs <archie.cobbs@gmail.com>
To: ivy-user@ant.apache.org
Sent: Monday, January 5, 2009 7:49:39 PM
Subject: Re: how to put the artifacts in ant classpath?

I'm not an expert but here's my comment :-)

I think we should simply change the comment from "Please prefer the use of
retrieve + standard ant path creation" to "You may want to prefer the use of
retrieve + standard ant path creation".

If you don't care about making your ant build "independent from ivy" then
there's no reason not to use ivy:cachepath.

-Archie

On Mon, Jan 5, 2009 at 12:44 PM, Alan Chaney <alan@writingshow.com> wrote:

> I wondered about this as well - I've been using ivy:retrieve to pull stuff
> into local folders and using that for the jar/war builds. This can get a bit
> messy, so I was quite interested in using ivy:cachepath when it was raised
> in this thread because then I would only have to have one copy of a
> particular jar on my local filing system (the one in the cache)
>
> But then I read the statement in the docs and became confused as to what
> "best practices" might be.
>
> Maybe that comment should be removed or clarified. Comments from Ivy
> experts would be gratefully appreciated.
>
> Thanks
>
> Alan Chaney
>
>
>
>
> paul.newport@targetgroup.net wrote:
>
>>
>>
>>
>> I wouldn't use cachepath, as one would normally not have the ivy cache
>> present on the deployment target.
>>
>> We use the ivy cache jars via IvyDE for compilation, but ivy retrieve for
>> pulling jars into wars.
>>
>>
>>
>> Target
>> www.targetgroup.net
>>  Target is a trading name of Target Group Limited, registered in England
>> and Wales No. 1208137
>> Registered office:  Target House, Cowbridge Road East, Cardiff CF11 9AU
>>
>> **********************************************************************
>> DISCLAIMER.
>> This message is intended only for the use of the Addressee and may
>> contain information that is PRIVILEGED and CONFIDENTIAL. If you are not
>> the intended recipient you must not copy, distribute or take any action or
>> reliance upon it. The content of this message may also contain personal
>> views of an employee of this company and does
>> not necessarily represent the view of the company.
>> **********************************************************************
>> This message has been scanned by Norton Anti-Virus. It has also been
>> scanned by MAILsweeper to enforce our e-mail policy. If you have any
>> concerns or comments about the content of this message, please  e-mail
>> support@targetgroup.net.
>> **********************************************************************
>>
>>
>> _____________________________________________________________________
>> This email has been scanned for all viruses by the MessageLabs Email
>> Security System. For more information on a proactive email security
>> service working around the clock, around the globe, visit
>> http://www.messagelabs.com
>>
>>
>> !DSPAM:49621a49272182136417547!
>>
>>
>>
>
>


-- 
Archie L. Cobbs