Peter Donald wrote:
On Fri, 28 Dec 2001 03:57, Berin Loritsch wrote:
I propose we publish distinct API groups. Most of the hard work is done
already with the package boundaries. The issue is when there are cross
package dependancies. Let's face it, Pools are easier to write with Buffers
and Mutexes. By doing this, we have to commit to documenting the
dependancies.
This is very close to my original desire for Excalibur which IIRC you
-1'ed!!! :)
Allow some room for people to grow. :)
The one difference - rather than "commit to documenting the dependancies" we
instead declare them in a properties file or something that would allow the
"Optional Package" manifest specifications to be generated for each jar and
thus the dependency tree could be automagically walked like that.
That would be part of the solution, but if a Pool requires Concurrent and
Containers, you have to tell the user that they are in different packages.
Otherwise, they will be in for a rude awakening.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
