We should see how small the dependency footprint can be. I'm sure that this is one of the goals of the MC as well. I know that this is an issue
with Seam we have many dependencies and users ask how can I slim it down.
* it still seems to be under pretty heavy development (docs are very
incomplete)
* what happens if WB RI uses one version of MC and the AS uses another?
What about conflicts with other containers caused by the MC. I know
that one of the goals of the MC is to be container agnostic, but I'm
sure there will be initial conflicts. WBs needs to work in any
container to be viable - if we get out of the gate quickly using the MC
- great! But initial impressions are important, and if we have
conflicts with other containers it might be seen a bit like Seam - as a
JBoss specific project - at least at first
:)
I'm not saying it is blocker to using the MC, but we should look into
container deployment issues.