I want to be clear about the extent of the change you are proposing. There are several points where you talk about "in the future", and I am not sure whether that means "now".
| Change the nukes.ear to a nukes.sar | | (Module?) war to have Nukes components with a nukes.xml that will be located in the war | | | Having the clean separation of resources and code + being able to dispatch to a JSP "view" are good things. | | In terms of doing the changes now versus waiting until after 1.1 (fixing existing modules) - you have some set of changes in core right now, and they do not effect the existing modules. So my questions are: | | | | Are there any other changes to the core that need to happen in order to implement the "new" way? | | | | If there are core changes needed, do those core changes break the existing modules if those modules are not changed as well? | | | | Is it possible to change a module to the "new" way without requiring them all to change at once? | | | | Are the changes to a module mechanical (just editing build scripts and config files), or will we really need to change a lot of code and retest? | | | | If we can do the change incrementally and in a short time period (a week?), then I say let's split the work up and do it against HEAD. Otherwise, we can branch CVS and merge it in later. | | Thoughts? | | | Sherman <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825064#3825064";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825064>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
