You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2006/01/10 22:02:21 UTC
[jira] Assigned: (DERBY-612) Add locale jars as ClassPath entries
in derby.jar
[ http://issues.apache.org/jira/browse/DERBY-612?page=all ]
Andrew McIntyre reassigned DERBY-612:
-------------------------------------
Assign To: Andrew McIntyre
> Add locale jars as ClassPath entries in derby.jar
> -------------------------------------------------
>
> Key: DERBY-612
> URL: http://issues.apache.org/jira/browse/DERBY-612
> Project: Derby
> Type: Improvement
> Components: Build tools, Documentation, Localization
> Reporter: Daniel John Debrunner
> Assignee: Andrew McIntyre
>
> Adding the locale jars (derbyLocale_es.jar, derbyLocale_de_DE.jar etc.) as ClassPath manifest entries in derby.jar would remove the need for users to add them to their class path. Thus the only jars required in the user's classpath would be:
> derbynet.jar - running network server (already brings in derby.jar)
> derby.jar - running embedded
> This would add to the ease of use for Derby. The manifest entries could be generated based off the list of locales or justr hardcoded in the build target for derby.jar (since they change infrequently).
> Since ClassPath entrries are ignored if the jars do no exist, this would do no harm in an environment where none or a subset of the locare jars are shipped.
--
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