Aside from the one definite alteration that Pete wants
to make to ConfigurationBuilder (adding URL access methods),
and the one he can't remember about, the API should be
pretty stable at this point.
I've set an arbitrary deadline for next Friday, May 4
2001 to be the end of changes for Avalon framework.
The only reason being that unless something glaring
comes up, we should be good to go. This doesn't mean
that if something comes up with the API after May 4,
we won't be able to do anything about it. All it
means is that we need to examine the API and if there
is something that bothers you, we should discuss it
now.
At this point, the build script needs to separate
Excalibur, AvalonAPI, and Test jars. Do I have
any takers?
VOTE: name of jars--
Framework -- "avalon.jar"
Excalibur -- "excalibur.jar"
Test classes -- "avalon-test.jar"
The next change to the build script is that we need
to make sure that testlets can be run.
Next, we need a testlet for every Excalibur component
that can be tested. The list of testlets already
created are:
cli
collections
datasource
io
pool
property
Which means we need to write testlets for:
component
concurrent (can this really be tested with a testlet?)
thread
Lastly, we need to make sure the testlets excersize the
excalibur components completely.
Not too glamorous, but are there any volunteers for these
tasks? I can write the testlet for component and fix
datasource testlet to use a dynamic jdbc driver. Peter,
you may have to take cli and property (just to make
sure they test everything).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
