Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4405DBEA.4080101@apache.org>
Date: Wed, 01 Mar 2006 09:37:46 -0800
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: derbytools.jar loading derbyclient.jar
References: <44034D3D.4050904@sbcglobal.net>
	 <54ac72d70602271131v51b76b0pb97b51e1f2c6d431@mail.gmail.com>
	 <44035C50.5030203@apache.org>
	 <54ac72d70602271221q576af892k3eb821d423a31101@mail.gmail.com>
	 <44036039.6030708@apache.org>
 <4403611E.1080505@sbcglobal.net>	 <54ac72d70602271626oa68627bvd9b3bb7f32fdd637@mail.gmail.com>
	 <4403A405.1050504@sbcglobal.net>
	 <54ac72d70602281658q776cd029of5e359d143cd8aad@mail.gmail.com>
	 <44051E29.2090904@sbcglobal.net>
 <54ac72d70602282049h4122b4e4qf9cea3521613b6c7@mail.gmail.com>
 <44053257.9090307@sbcglobal.net> <4405D87E.60101@amberpoint.com>
In-Reply-To: <4405D87E.60101@amberpoint.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bryan Pendleton wrote:
> Here's a thought for a totally different approach to solving
> the original problem, which I will unfairly summarize as:
> 
>   Make it easier for brand new users to run Derby in trial
>   situations without having to learn a lot about scripts and
>   CLASSPATH settings.
> 
> What if we shipped two configurations of the Derby classes:
>  - the first configuration is the current one, with the Derby
>    classes broken out into the separate jars. Each jar
>    continues to be independent (no Class-Path manifest entries)
>  - the new configuration is a single jar ("derbyall.jar", say)
>    which has all the classes from derby.jar, derbytools.jar,
>    derbynet.jar and derbyclient.jar in a single jar file.
> 
> Then, the "new user" tools and examples could just tell users
> to run things like
> 
>    java -jar derbyall.jar ij
>    java -jar derbyall.jar NetworkServerControl start
> 
> While the more advanced user, who wants to carefully load only
> the necessary classes, mix-and-match versions, etc., could
> continue to use the separate jar files as they did before.
> 
> What do you think? Does an approach like this offer any value?

That's a great idea, I would add one minor modification.

Don't have the classes in derbyall.jar, just Class-path entries.

Class-Path: derbynet.jar derbytools.jar derbyclient.jar

Then it's (almost) the same functionality for almost zero overhead.

The name may want to change as well, something that indicates it's
really only for use as a command line tool. derbycmd.jar doesn't quite
seem right, maybe others have better ideas.

Dan.