Anyone entertains the idea of making Clustering a top level project, e.g., as a standalone release?
It can contain: tomcat clustering (standalone and embeded), HA-jndi (standalone and embeded), DRM (or a version of distributed RPC), HA-Remoting, ejb3 clustering, etc. Of course, all the integrtion codes will still need to reside under current head. But I am thinking we can modularize most of Clustering (plus Tomcat) module. That way, it has its own release cycle wrt to AS or ejb3. -Ben -----Original Message----- From: Adrian Brock Sent: Tuesday, September 13, 2005 10:16 AM To: Ben Wang Cc: jboss-development@lists.sourceforge.net; Jerry Gauthier; [EMAIL PROTECTED]; QA Subject: RE: [JBoss-dev] RE: [jboss-cvs]jbossmx/src/main/org/jboss/ha/jndi/treecache ... On Tue, 2005-09-13 at 12:36, Ben Wang wrote: > Yes, untill Jira can do a cross-project monitoring, I still the need > to maintain a separate Jira for clustering. My argument is exactly the opposite. Because JIRA does not have cross project monitoring, maintanence of this JBossAS component should be in the JBossAS project. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
