Is there such a thing as a super-clean ant build target, to return the
checkout to a pristine state?
An absolutely pristine branch_4x svn checkout takes up about 267MB of
disk space. After 'ant compile' in the checkout root, that increased to
411MB. Following that with 'ant clean' dropped it to 352MB - MUCH
larger than the pristine checkout.
I then changed to the solr directory and did 'ant dist' which bumped the
size to 489MB, and then back to the root with another 'ant clean' which
dropped to 359MB.
It looks like the additional space is consumed by jars in various lib
folders. While doing tests for SOLR-1972 earlier today, I ran into a
problem where ant-1.8.2.jar was zero bytes. This is one of the files
that is not in a clean checkout - it gets pulled down by Ivy. I had no
way to go back to a pristine checkout, so I wiped the entire directory,
checked it out fresh, and reapplied the patch. That worked. I probably
could have just erased the one bad jar, but I didn't know if it would be
safe to monkey with the build system in that way.
If there had been a way to get back to a pristine checkout, I wouldn't
have needed to increase load on Apache's network. When I'm at work, I
have more bandwidth than I could ever use and a checkout is very very
fast, but that's not the case for many people, and it's definitely not
the case for my home network.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
