sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SIS-337) Package EPSG Derby DB in ​sis-epsg jar, eliminating the need for external SIS_DATA dir
Date Tue, 22 Nov 2016 20:27:00 GMT

    [ https://issues.apache.org/jira/browse/SIS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687798#comment-15687798
] 

Martin Desruisseaux commented on SIS-337:
-----------------------------------------

Actually the reason why org.apache.sis.non-free:​sis-epsg artifact contains the SQL scripts
rather than the Derby database itself is because the database can be installed not only on
Derby, but also on HSQL, PostgreSQL or MS-Access. Derby is the default database but the user
can choose another one. A Derby database embedded directly in the JAR file would need to be
done as a separated artifact (maybe {{sis-epsg-derby}}) provided for convenience.

> Package EPSG Derby DB in ​sis-epsg jar, eliminating the need for external SIS_DATA
dir
> --------------------------------------------------------------------------------------
>
>                 Key: SIS-337
>                 URL: https://issues.apache.org/jira/browse/SIS-337
>             Project: Spatial Information Systems
>          Issue Type: Wish
>          Components: Referencing
>    Affects Versions: 0.7
>            Reporter: Kevin Mehall
>
> Since [Derby supports|https://db.apache.org/derby/docs/10.7/devguide/cdevdeploy11201.html]
read-only databases in .jar files, is there a reason that the `org.apache.sis.non-free:​sis-epsg`
package includes SQL source to create an external database, rather than the database itself?
> It would make deployment much easier if there were no need for a SIS_DATA directory and
environment variable, and adding the dependency were the only thing necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message