To what degree are we going to decompose the source tree? Take the example in the link previously given:
http://docs.jboss.org/process-guide/en/html/structure.html Without additional refactoring to reduce dependencies, extracting the Remoting module would require the extraction of 9 other existing modules. The Remoting module may currently be overly-coupled, but surely there is some coupling there that is legitimate. So we will need to be able to deal with some level of decomposition whether or not we extract every module. If a component is only going to be released as a part of the application server, it makes sense to keep it in that source tree. But if it is going to be released as part of more than one project, it will need to be extracted. So, to make this concrete, the criteria for extraction is: 1. Is it useful outside of the AS as standalone project? 2. Will it be released as a part of more than one container project? 3. Is it a dependency of a project which falls under #1 or #2? #2 is predicated on the assumption that we will have multiple integation projects. We currently have one container project -- the AS. If we have, say, a seperate POJO Server project, it seems like we would want many services to be included in both projects. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861509#3861509 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861509 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
