Then either head should be moved to svn so that project refactoring can be done with history maintained, or these modules be removed from jboss-head and reintegrated as binary dependencies so that they can be migrated seperately.
I doubt a complete move is practical given the J1, JBW timeline coming up. common already has been broken out to svn: http://anonsvn.jboss.org/repos/ + http://anonsvn.jboss.org/repos/common-core/ + http://anonsvn.jboss.org/repos/common-logging/ + http://anonsvn.jboss.org/repos/common-xb/ This has to be moved to a real read/write repository and resynched with cvs. Aop and test need to follow suite. Getting the svn repository setup has been the bottleneck in most migrations. > -----Original Message----- > From: Adrian Brock > Sent: Tuesday, May 02, 2006 3:14 AM > To: Scott M Stark > Cc: Ryan Campbell; Bill Burke; QA; > jboss-development@lists.sourceforge.net > Subject: RE: jboss-head-jdk-matrix Build Failed > > When JBossXB, common, test and aop are properly standalone. > > I've still not seen something I can manage in this respect. > > Cache, Remoting, Webservices maybe happy to run before they can walk, > I am not. > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
