On 18 Nov 2011, at 14:12, Ate Douma 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). > > 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 this definitely doesn't need to be in svn. I'd been assuming it was some sort of local svn issue at my end, glad to know its not just me. > >> >> Ross >> >> On 18 November 2011 13:43, Ate Douma<[email protected]> wrote: >>> On 11/18/2011 02:37 PM, Ross Gardler wrote: >>>> >>>> On 18 November 2011 13:18, Ate Douma<[email protected]> wrote: >>>>> >>>>> On 11/18/2011 01:59 PM, Ross Gardler wrote: >>>>>> >>>>>> On 18 November 2011 12:54, Ate Douma<[email protected]> wrote: >>>>>>> >>>>>>> I've just updated to the latest wookie trunk and ran >>>>>>> >>>>>>> $ ant clean >>>>>>> $ ant run >>>>>>> >>>>>>> I've build wookie last time for the 0.9.1 release candidate so I expect >>>>>>> to >>>>>>> have most/all external dependencies in my local ivy cache (which is >>>>>>> where?), >>>>>>> no? >>>>>>> >>>>>>> However the ant run build took more than 15 minutes to complete! >>>>>>> Should I have some magic setting to speed this stuff up? >>>>>> >>>>>> I always use ant run -Doffline=true which prevents a check of the >>>>>> dependencies, but I wouldn't expect it to make 15 mins difference. >>>>>> >>>>>> I've not done a clean build for some time, I wonder if the clean is >>>>>> killing the downloaded artifacts? Even if it is 15 minutes seems >>>>>> excessive >>>>> >>>>> OK, thanks for the tip. >>>>> >>>>> I've tried it again with >>>>> $ ant clean >>>>> $ ant -Doffline=true compile-test >>>>> >>>>> But it still goes 'online' trying to resolve dependencies... >>>> >>>> Interesting. >>>> >>>> I'm running it right now and it seems to be taking its time in the >>>> resolve target (just after finding org.jdom). It's been stuck there >>>> for 7 minutes already. >>>> >>>> Looks like there is a network problem, but it's supposed to be offline. >>> >>> My above build finally finished after this time taking 28 minutes, 13 >>> seconds. >>> As it almost doubled up now, I agree there must be a network problem (too). >>> However, something like the -Doffline=true should be made to work properly >>> as I cannot wait on this like all day :) >>> >>>> >>>> Ross >>> >>> >> >> >> >
