[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Participation
|
On 26 Jan 2009, at 13:32, Pascal Rapicault wrote: What is the derbytools.jar for?
In addition, there are Derby utilities that are system procedures that you can call by using the ij tool. For example, there are system procedures that you can use to import and export external files. Instructions on how to use these system procedures are included in the Derby Tools and Utilities Guide and the Derby Reference Manual.
* Running sysinfo
The Derby sysinfo tool displays information about your Java environment and your version of Derby.
* Running ij
The Derby ij tool is a JDBC tool that you can use to run scripts or interactive queries against a Derby database.
* Running dblook
The Derby dblook utility is a Data Definition Language (DDL) generation utility.
Possibly this would best be a separate. One could argue that this, the derby.war, derbyrun.jar do not belong in orbit because it is doubtful that they would ever be delivered as a part of an Eclipse project. However, my experience are that they are useful pieces of Derby during development. Therefore, if they are not approved by EMO-IP (which they are now) and not available in Orbit, then each developer on a project using Derby will have download there own as the project team cannot put it in their SVN/CVS. Repetitive work and an opportunity for release mismatches.
What are you planning on doing for the translation fragments? Do you want to deliver them as individual fragments?
I had not planned on it, I was thinking of a single fragment. There are 13 language jars, each weighing in at approximately 100k. The way that I see it, is that in most cases an Eclipse project is either interested in delivering Derby i18n or not, so they will likely include all or none.
If you or others differ, I would be happy to bundle the separately.
Joel
PaScaL
<graycol.gif>Joel Rosi-Schwartz ---01/25/2009 08:05:08 AM---Hi, I have been speaking with ZX about participation on Orbit and would
<ecblank.gif>
From: | <ecblank.gif>
Joel Rosi-Schwartz <Joel.Rosi-Schwartz@xxxxxxxxx> | <ecblank.gif>
To: | <ecblank.gif>
orbit-dev@xxxxxxxxxxx | <ecblank.gif>
Date: | <ecblank.gif>
01/25/2009 08:05 AM | <ecblank.gif>
Subject: | <ecblank.gif>
[orbit-dev] Participation |
Hi, I have been speaking with ZX about participation on Orbit and would like to declare my interest in doing so. The first thing I am going to undertake is the bundling of Derby Version: 10.4.1.3 for CQ #2500 since my CQ 2568 is dependent on it. If it is agreeable, I plan on creating two bundles. The first would be minimal and follow the same structure and contents as the Orbit bundling for Derby 10.1.2. The second would maintain the same logical structure, but would contain all of the jars for a full Derby delivery: derby.jar
derby.war --- I question if this one is appropriate. Possibly a separate bundling?
derbyLocale_cs.jar
derbyLocale_de_DE.jar
derbyLocale_es.jar
derbyLocale_fr.jar
derbyLocale_hu.jar
derbyLocale_it.jar
derbyLocale_ja_JP.jar
derbyLocale_ko_KR.jar
derbyLocale_pl.jar
derbyLocale_pt_BR.jar
derbyLocale_ru.jar
derbyLocale_zh_CN.jar
derbyLocale_zh_TW.jar
derbyclient.jar
derbynet.jar
derbyrun.jar --- I would need to investigate the appropriateness of inclusion
derbytools.jar This has been approved by EMO-IP. I would appreciate you comments before I begin. Thanks, Joel P Please consider the environment before printing this e-mail. Thank you. Joel Rosi-Schwartz Joel.Rosi-Schwartz@xxxxxxxxx Etish Limited http://www.etish.org/ ORMF and Useme http://www.eclipse.org/ormf _______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
