On 1/26/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote: > > - improve the bundled scripts to be easier to use > - re-arrange the directory structure to be more obvious (I was > certainly confused by the concept of a "framework" when I first > started with Derby). > - issue better error messages for misconfiguration problems.
These are all excellent ideas. I had a few ideas to improve the scripts as well: - change the name of the framework directory to bin and collapse the directory structure. - change DERBY_INSTALL to DERBY_HOME to make it similar to other projects' use of a HOME variable - use the DERBY_HOME variable to self-configure as much as possible. - improve the scripts to detect whether you are in a client/server or embedded environment and do the right thing for the tools that work differently in the two environments. I'm sure other people have ideas on ways to improve the scripts to get people up and running faster. Because some of them are fairly straightforward, although I believe there's an impact on the docs particularly with the DERBY_INSTALL -> DERBY_HOME change. Lance Andersen also mentioned he would prefer an alternative to scripts altogether, such as Ant based task files. If no one objects to the changes above, though, I can file JIRA entries for them and start looking into doing them. andrew
