> * * Definition of Specification requirements * *
> Specifications are evolvable, meaning at the point of a release, they have
a
> version and what is in it is set in stone. There can not be any changes to
> the specification, and any 'undefined' areas must remain undefined until a
> revised versi
Niclas Hedhman wrote:
TCK Harness for Containers have the problems of Inversion of Control, where it
needs to invert (!) that. Perhaps there needs to be a Specification for
Container Testability. The only alternative that I can see is that the
Container provides the TCK Harness itself.
I think
Gang,
I am sketching on the "TCK issue" and have identified some concerns that I
would like to share and discuss.
* * Definition of Specification requirements * *
Specifications are evolvable, meaning at the point of a release, they have a
version and what is in it is set in stone. There can n
