Hello, sorry for the cross-posting but this is about geosever and geotools builds in ares.
The build process leaves a lot, literally thousands, of files and directories in the temp directory. I cam across this looking for the reason some geogig temp directories are also left over where they shouldn't because we're supposed to be using junit's TemporaryFolder everywhere, and turns out we missed a couple. So, the "right way" of solving this inconvenience would be to upgrade all geotools and geoserver unit/integration tests to use a TemporaryFolder rule. Now, that'd be a pretty monumental task. But I came up with this other idea: we can clean up after the build in the shell script that's executed, and isolate the temporary resources of each projects on their own temp folder with the -Djava.io.tmpdir system property. In a nutshell: - have /tmp/getotools-<version> and /tmp/geoserver-<version> directories - run maven with mvn -Djava.io.tmpdir=/tmp/geotools|geoserver-<version> - run rm -rf /tmp/geotools|geoserver-<version>/* in the post-build shell script and voilá. Moreover, ares doesn't have it's /tmp in its own partition, and there's a tmpfs (i.e. memory) mounted at /mnt/memtmp which we use to speed up the geogig build (that is, running tests that do IO in a tmpfs). Would you guys be interested in doing that too? Best regards, Gabriel -- Gabriel Roldán Software Developer | Boundless <http://boundlessgeo.com/> grol...@boundlessgeo.com @boundlessgeo <http://twitter.com/boundlessgeo/>
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
