Andrea Aime wrote: > I'm ok to put up with extensive build time and high memory usage for > a short time, provided there are serious plans to address both, > one way or the other. GeoTools has already bad rep enough without > having to require a server like setup to build it (512M heap > mean 600-700MB of real memory consumption factoring in the extra > stuff the VM is loading)
Agreed. > Another option could be to have the build server build with > -Pextensive (shall we rename this to -Pexpensive ;-) ?) +1 for the rename. > and leave the random developer without the extra burden. Jody has suggested using -Pextensive. We could also make our own "app-schema-bloat-bloat-bloat" profile that we enable on our CI box. Either of these would, in effect, disable some tests, and would infringe on my TDD religious obligations. ;-) We (Rini and I) need to fix the bloat. -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
