ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Marks <topher1...@gmail.com>
Subject Re: Just the artifact I want...
Date Wed, 23 Mar 2011 15:03:27 GMT
I don't regularly wipe our cache, but it's certainly possible. When I
reference one of my own modules, I generally add 'changing=true' to the
dependency definition. This always checks the repository for an updated
module.

Topher
On Mar 23, 2011 8:52 AM, "Richard_Senior" <richard.senior@gmail.com> wrote:
>
>
> topher1120 wrote:
>>
>> I believe it does the same, just in a different scope. I personally use
>> the
>> attribute on "dependency" so I can pick and choose.
>> Thanks,
>> Topher
>> On Mar 23, 2011 8:25 AM, "Richard_Senior" <richard.senior@gmail.com>
>> wrote:
>>
>
> Yes your solution is perfect. It suits the way I'm using ivy.
>
> If I can be cheeky and ask another question :) ....
> So far I have only compiled a single module that requires no other
modules.
> But now I'm about to start compiling a module that uses my first module.
>
> At the moment I have a single Cache that just stores my commons, spring,
> junit etc.
> That cache will never need wiping.
>
> But my idea is to have a separate cache that I can wipe at the start of
> every build, into which all my modules are published.
> Do you think this is the right way to do it? Can you offer me any tips?
>
> --
> View this message in context:
http://old.nabble.com/Just-the-artifact-I-want...-tp31219841p31220507.html
> Sent from the ivy-user mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message