On 1/18/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
So this now brings me to the question of assemblies. For M1 we shipped Tomcat and Jetty versions with CXF and OpenJPA. As we talked about in another thread there isn't really a way to generate all the permutations of different assemblies I think for M2 we would ship the same configurations and in parallel have a discussion on packaging for when we get to the beta's so that users and better pick the versions of the software they want.
This makes a lot of sense to me for M2. As I recall a patch was posted on dev that allows users to enable axis. Since someone has already asked about axis support in M2 perhaps that patch should be offered in a more conspicuous area. For the beta, I think giving the users a choice is the best approach as long as we: 1.) provide reasonable and TCK tested defaults 2.) help them make informed decisions about changing the defaults 3.) make it easy to enact their decisions 4.) allow them to change their minds Providing all the permutations of different assemblies for download doesn't meet any of those criteria, except for maybe #3. Offering a single assembly that has passed TCK and the alternate modules as plugins may get us closer to the mark. Best wishes, Paul
