If we do start shipping 8 (or more) different assemblies... which I
think is crazy, then we probably don't want to hook them all up to
the default build, as it will just cause it take longer and longer to
run.
We really need to get plugins functional so that we can build one
assembly.
Please... :-)
--jason
On Jan 12, 2007, at 8:52 AM, Matt Hogstrom wrote:
I understood the point but since every permutation takes at least
two days, hardware, and time to nurture I was more concerned about
getting in a situation where we wouldn't release anything until we
had 8 different assemblies.
On Jan 12, 2007, at 3:22 AM, Alan D. Cabrera wrote:
On Jan 11, 2007, at 7:27 AM, Matt Hogstrom wrote:
What are the specifics around claiming certification? My
understanding is that to claim an assembly as certified that
specific configuration is tested and made available. Apart from
that we can ship any permutation but cannot claim those as
certified. So if we TCK tested:
Tomcat Axis OpenJPA and
Jetty CXF Cayenne
then
Tomcat CXF OpenJPA would not be considered a certified release.
It would most likely work but we couldn't claim that specific
assembly as certified.
Is that correct?
I think that you are correct but I think that you may have missed
David's point in that there would be almost no work in testing new
combinations once the constituent parts have been tested in
previous combinations.
Regards,
Alan
Matt Hogstrom
[EMAIL PROTECTED]
