I don't think its just TCK. I agree we should scope the
configuration to a limited set but I'm also concerned about making
assemblies available. Given my math challenged 6 which is really 8 I
don't think we would want to generate every one of them. So I think
from the download page perspective I think we need to identify the
assemblies which may be something like:
Jetty Axis OpenJPA
Tomcat CXF OpenJPA
(I'm not sure of the state of Cayenne)
The provide a "stubbed out" version that would allow a user to
install their preferred component via a plugin.
Just a thought.
On Jan 8, 2007, at 9:53 AM, Jason Dillon wrote:
On Jan 8, 2007, at 12:38 AM, David Jencks wrote:
rather than saying we'll only ship when we have all 6 it seems
more appropriate to me to say that we'll ship the assemblies that
people are willing to work on which includes TCK testing. Any
other ideas on how to handle this? Anyone interested in a
specific configuration and want to step up to TCK testing?
I think maybe we should concentrate on packaging things as
plugins, although this doesn't really affect what we run through
the tck.
Do we really need to run the TCK on every possible permutation? Why
don't we bless a specific configuration and then concentrate the
TCK effort on that specific assembly?
--jason
Matt Hogstrom
[EMAIL PROTECTED]
