Skip to:
ResourcePool.readStyle uses Resource.in() without checking if the file exists.
The current implementation simply creates the file. This is the last of three obvious cases where files are created spuriously.
If this is resolved, the main issue [GEOS-10705] can finally be resolved, too
I just resolved #6335.
If this gets accepted I can proceed with refactoring FileSystemResource (GEOS-10705).
FileSystemResource
ResourcePool.readStyle uses Resource.in() without checking if the file exists.
The current implementation simply creates the file. This is the last of three obvious cases where files are created spuriously.
If this is resolved, the main issue [GEOS-10705] can finally be resolved, too