On 18 November 2011 14:27, Ate Douma <[email protected]> wrote:
> On 11/18/2011 03:19 PM, Ross Gardler wrote:
>>
>> On 18 November 2011 14:12, Ate Douma<[email protected]>  wrote:
>>>
>>> On 11/18/2011 02:59 PM, Ross Gardler wrote:
>>>>
>>>> Ate,
>>>>
>>>> Please SVN up and try again. It looks like the cache was set to always
>>>> check the origin in the ant/ivysettings.xml file. I've changed this
>>>> and now -Doffline=true appears to be working for me.
>>>
>>> Did you check that in?
>>> I just did a SVN up but get no incoming changes (yet).
>>
>> There must have been an error in my commit (more network issues). This
>> time I have checked the output of my "svn ci"
>
> I've got your update and did an svn up.
> However, it still isn't working :(
>
> Is using the parameter -Doffline=true the correct one?
> I've just killed my local build as it still is going 'online' here.

OK, I dug a little deeper. My solution should route around the network
issue, but for some reason "ant clean" is also cleaning the ivy cache.
This, of course, means ivy is forced back online again.

So it was both a network and an ivy issue. Ivy appears to "helpfully"
go online if it really has to, even when you specify offline=true

I've stopped the cache being cleaned. I have a slow build underway
right now while Ivy rebuilds its cache, but I imagine that subsequent
clean builds will be quick.

Ross





>
> Note: I did (and want to be able to) $ ant clean first...
>
>>
>>> BTW: I now have a conflicting change on the WebContent/WEB-INF/lib
>>> folder.
>>>
>>> This WEB-INF/lib folder is empty in SVN, but seemingly the build itself
>>> removes it (ant clean?). This throws Eclipse/SVN into confusion.
>>> Is there a need to have this (empty) lib folder checked in?
>>> I think it would be better to *not* have this checked in and mark it with
>>> svn:ignore.
>>
>> +1
>
> Please make it so :)
>
>>
>> I think this is a legacy thing.
>>
>> Ross
>
>



-- 
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com

Reply via email to