[ 
https://issues.apache.org/jira/browse/SIS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Desruisseaux closed SIS-366.
-----------------------------------
    Resolution: Fixed

Close as "partially fixed" for Apache SIS 0.8, and "will not fix" for Apache 
SIS 1.1 (we can only declare "fixed" in JIRA status). This issue is not 
relevant anymore to Apache SIS since the PROJ wrappers moved to an external 
project. See SIS-510 for more information.

> sis-gdal module should not write native file in the temporary directory
> -----------------------------------------------------------------------
>
>                 Key: SIS-366
>                 URL: https://issues.apache.org/jira/browse/SIS-366
>             Project: Spatial Information Systems
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.7
>         Environment: Linux, MacOS
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             Fix For: 0.8
>
>
> The {{sis-gdal}} module uses Java Native Interface (JNI) for accessing the 
> Proj.4 library. Currently, the JNI are pre-compiled in 
> {{storage/sis-gdal/src/main/resources/native/<OS>/libproj-binding.so}} files 
> where {{<OS>}} is {{linux}} or {{darwin}}. The file size is about 14 kb. 
> Since we can not load a library from a JAR file, we have to copy it as a 
> regular file somewhere. Current implementation copies it in the temporary 
> directory.
> Problem is that some environments do not give execution permission in the 
> temporary directory. Consequently we should save the {{libproj-binding.so}} 
> files somewhere else. Some possibilities are:
> 1. Platform-specific directory like {{<user directory>/Library}} on MacOS.
> 2. A sub-directory of {{$SIS_DATA}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to