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.newp...@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 supp...@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!


Reply via email to