db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: Packaging
Date Tue, 31 May 2005 18:06:22 GMT
You might want to take a look at DERBY-289 ("enable code sharing between 
Derby client and engine").  Any rearrangement of jar files should 
probably take this into consideration.


Jeremy Boynes wrote:

> Currently we have:
> * derby.jar (embedded, engine)
> * derbynet.jar (network server)
> * derbyclient.jar (network client)
> I would like to add derbyserver.jar which includes everything from all 
> of these to form a complete standalone server; the client is included so 
> that people don't need to switch classpath if they want to use a remote 
> server and so that stored procedures can access remote servers.
> If we do this was can also potentially drop derbynet.jar as it is not 
> usable without derby.jar.
> Any objections?
> -- 
> Jeremy

View raw message