Looks good so far, some comments suggestions:
1) We need a section on what jars the user needs on the client and server classpaths,
e.g.
If you're using core, you need:
jbm-core-core-client.jar
if you're using netty you need netty.jar
if you're using jms you need jbm-jms-cllient.jar (we should have separate jar for jms
*client* stuff)
If you're using log4j you need.. blah blah
3)
We should also take the javax.jms.* interface classes out of jboss-jee.jar and put them in
their own jar so the user doesn't have to include *all* the jee classes.
4) Also I think we should take all the jars that the JBoss MC needs to run, unzip them and
rebuild them into another jar jboss-mc.jar (or whatever) and distribute that, this will
greatly limit and simplify the number of jars we distribute.
5) jboss-logging.jar has dependencies to both log4j *and* jboss as logging. Is this right?
I don't think we should expect users who just want to use log4j to include all the
jboss as logging jars!
6) Why are we including jbm-ra.jar in the distro? Isn't jbm-ra.jar sufficient?
7) JAASSecurity manager should be in core, not integration layer, since JAAS is standard
part of JDK now. (I have moved this).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232628#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...