db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1032) Create new scripts which follow common practice at Apache
Date Fri, 11 Aug 2006 05:14:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1032?page=comments#action_12427419 ] 
Andrew McIntyre commented on DERBY-1032:

Committed derby-1032-v2.diff to trunk with revision 430668 (unix scripts) and 430677 (windows
scripts). Two commits were necessary so that the files have the proper native line endings.
To resolve this issue completely, we would need to include the new scripts in the -bin distribution
and the snapshots and mark the frameworks scripts as deprecated in all the appropriate locations.
The frameworks scripts could probably be removed from the snapshots immediately.

> Create new scripts which follow common practice at Apache
> ---------------------------------------------------------
>                 Key: DERBY-1032
>                 URL: http://issues.apache.org/jira/browse/DERBY-1032
>             Project: Derby
>          Issue Type: Improvement
>          Components: Demos/Scripts
>    Affects Versions:
>            Reporter: Andrew McIntyre
>         Assigned To: Andrew McIntyre
>            Priority: Minor
>             Fix For:
>         Attachments: derby-1032-bin-sh.tgz, derby-1032-v1.diff, derby-1032-v2.diff
> Scripts for Derby should be written to follow common practice at Apache. This means locating
them in a bin directory, and self configuring from the minimum amount of information necessary:
installation location and in our case, the location of Java, from the variables DERBY_HOME
and JAVA_HOME respectively. If these variables are not set, we should report this to the user.
Good examples are available in Ant, Forrest, and Maven, and much of the same setup code can
be reused from those projects.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message