I was thinking about M2 this weekend and was considering many of the
challenges we face in putting out certified releases. Up till now
the number of permutations has been pretty limited and that has been
Jetty and Tomcat. With Java EE 5.0 life is no longer that simple.
Here are the choices I know of today:
Web Container (Tomcat / Jetty)
WebServices (Axis 2 / CXF)
EJB 3.0 Persistence (OpenJPA / Cayenne)
I think this makes 6 different assemblies and of course 6 separate
certification efforts. Perhaps we can do this and perhaps we can't.
Based on where projects are at and their desire to participate in
helping to integrate (and do TCK testing :).
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?
Matt Hogstrom
[EMAIL PROTECTED]
