ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Coene <maarten_co...@yahoo.com>
Subject Re: how to put the artifacts in ant classpath?
Date Mon, 05 Jan 2009 22:02:58 GMT
Here is how I use it:

I always use ivy:cachpath for "building" tasks like:
- compilation
- junit testing
- PMD/Checkstyle/... reporting

I only do a retrieve when creating a zip, war or ear (or anything else that will be distributed)
so it can be installed/deployed independently.

Maarten




----- Original Message ----
From: Alan Chaney <alan@writingshow.com>
To: ivy-user@ant.apache.org
Sent: Monday, January 5, 2009 8:02:11 PM
Subject: Re: how to put the artifacts in ant classpath?

Yes, that makes sense, because after all the build file is probably 
already dependent upon ivy
(it will have all the ivy resolve stuff in it at the very least.)

Another thought (I'm not sure if this is OT) - what does IvyDE for 
eclipse do? I've been trying to
find the time to work out whether I should go that route. It would make 
sense to stick to a consistent
policy within my organization at least.

Alan


Archie Cobbs wrote:
> 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
>>>
>>>
>>>
>>>
>>>
>>>
>>>      
>>    
>
>
>  


      

Mime
View raw message