I don't think so -- it just reloads the config file over and over but it's probably in the os cache anyway.
That property passing is broken as I explained. In general antcalls lead to a big mess with references/ properties, I hate it (but don't have an idea how to improve it). Dawid On Thu, Jul 5, 2012 at 1:21 PM, Chris Male <[email protected]> wrote: > Is your workaround particularly slow? > > > On Thu, Jul 5, 2012 at 11:18 PM, Dawid Weiss <[email protected]> > wrote: >> >> Ok, I know why this is happening. We have <antcall> and <ant> calls >> across build files. Sometimes these calls pass only selected >> properties (propertysets) but do not pass references. As in here: >> >> <ant dir="${common.dir}" target="default" inheritall="false"> >> <propertyset refid="uptodate.and.compiled.properties"/> >> </ant> >> >> ivy:configure stores the default configuration as a reference so the >> property will be passed down but the reference not. I don't know how >> to fix it cleanly so I'll just leave my workaround patch in (which >> re-reads the configuration every time, unfortunately). >> >> Dawid >> >> On Thu, Jul 5, 2012 at 12:52 PM, Dawid Weiss >> <[email protected]> wrote: >> > This has to do with ivy -- I admit I don't know what's happening. The >> > configuration gets read once but it isn't persisted for other ivy >> > tasks (even though the property clearly is): So you end up with: >> > >> > ivy-configure: >> > >> > resolve: >> > [ivy:retrieve] :: loading settings :: url = >> > >> > jar:file:/home/hudson/.ant/lib/ivy-2.2.0.jar!/org/apache/ivy/core/settings/ivysettings.xml >> > [ivy:retrieve] >> > [ivy:retrieve] :: problems summary :: >> > [ivy:retrieve] :::: WARNINGS >> > [ivy:retrieve] module not found: >> > com.carrotsearch.randomizedtesting#junit4-ant;1.6.0 >> > [ivy:retrieve] ==== local: tried >> > [ivy:retrieve] >> > >> > /home/hudson/.ivy2/local/com.carrotsearch.randomizedtesting/junit4-ant/1.6.0/ivys/ivy.xml >> > [ivy:retrieve] -- artifact >> > com.carrotsearch.randomizedtesting#junit4-ant;1.6.0!junit4-ant.jar: >> > [ivy:retrieve] >> > >> > /home/hudson/.ivy2/local/com.carrotsearch.randomizedtesting/junit4-ant/1.6.0/jars/junit4-ant.jar >> > [ivy:retrieve] ==== shared: tried >> > [ivy:retrieve] >> > >> > /home/hudson/.ivy2/shared/com.carrotsearch.randomizedtesting/junit4-ant/1.6.0/ivys/ivy.xml >> > [ivy:retrieve] -- artifact >> > com.carrotsearch.randomizedtesting#junit4-ant;1.6.0!junit4-ant.jar: >> > [ivy:retrieve] >> > >> > /home/hudson/.ivy2/shared/com.carrotsearch.randomizedtesting/junit4-ant/1.6.0/jars/junit4-ant.jar >> > [ivy:retrieve] ==== public: tried >> > [ivy:retrieve] >> > >> > http://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/junit4-ant/1.6.0/junit4-ant-1.6.0.pom >> > [ivy:retrieve] -- artifact >> > com.carrotsearch.randomizedtesting#junit4-ant;1.6.0!junit4-ant.jar: >> > [ivy:retrieve] >> > >> > http://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/junit4-ant/1.6.0/junit4-ant-1.6.0.jar >> > [ivy:retrieve] module not found: >> > com.carrotsearch.randomizedtesting#randomizedtesting-runner;1.6.0 >> > [ivy:retrieve] ==== local: tried >> > >> > Note that sonatype's release repository is NOT tried, it just checks >> > the default chain. I'll provide a workaround fix in a second but I >> > don't know how to fix it in a proper way. >> > >> > Dawid >> > >> > On Thu, Jul 5, 2012 at 12:47 PM, Apache Jenkins Server >> > <[email protected]> wrote: >> >> Build: https://builds.apache.org/job/Solr-4.x/28/ >> >> >> >> No tests ran. >> >> >> >> Build Log: >> >> [...truncated 8055 lines...] >> >> >> >> [...truncated 8055 lines...] >> >> >> >> [...truncated 8055 lines...] >> >> >> >> [...truncated 8055 lines...] >> >> >> >> [...truncated 8055 lines...] >> >> >> >> [...truncated 8055 lines...] >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Chris Male --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
