sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Desruisseaux (JIRA)" <>
Subject [jira] [Resolved] (SIS-118) Provide convenience shell script for launching the command-line
Date Wed, 21 Aug 2013 15:40:52 GMT


Martin Desruisseaux resolved SIS-118.

       Resolution: Fixed
    Fix Version/s: 0.3

Provided the script in the 0.3 release. For now it includes only a Unix script, not yet a
Window script.
> Provide convenience shell script for launching the command-line
> ---------------------------------------------------------------
>                 Key: SIS-118
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: New Feature
>          Components: Command line
>    Affects Versions: 0.3
>            Reporter: Martin Desruisseaux
>            Priority: Minor
>             Fix For: 0.3
> Currently, the easiest way to launch the command-line is to use the following syntax
on the JAR file decompressed from the PACK200 file:
> {noformat}
> java -jar sis.jar
> {noformat}
> However the syntax is slightly more complicated if someone wants control on the classpath,
for example in order to include the UCAR NetCDF libraries (an optional dependencies). We may
consider providing a small shell script making SIS usage easier.
> We could provide a ZIP bundle with the following files:
> * {{README}}
> * {{LICENSE}}
> * {{NOTICE}}
> * {{bin/sis}}
> * {{bin/sis.bat}}
> * {{bin/sis.pack.gz}}
> * {{etc/}}
> * {{ext/}}
> * {{log/}}
> The {{bin/sis.pack.gz}} file would be automatically uncompressed into a {{sis.jar}} file
by the {{bin/sis}} or {{bin/sis.bat}} scripts when first needed.
> {{ext/}} would be an initially empty directory where user can put optional dependencies
if we wishes (e.g. UCAR NetCDF library).
> {{log/}} would we an initially empty directory where we would send log files (e.g. the
Derby database log files).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message