JBBUILD-307 subtasks: 2. "Create script to modify a SVN jbossas repo and change the directories to the proper names" is certainly a show stopper as the migration of the cvs modules does not honor the cvs module aliases. The jboss-head or jboss-4.0.x tag/branch from cvs contains the raw cvs module names and so is not buildable.
6. "Investigate and document the process for extracting a module's src into its own repository" is certainly not a show stopper. 4,5,7 are all related to does svn tagging/branching/comparision work with the existing tools. The idea svn plugin seems rather poor (in fact, non-existent) in terms of being able to compare a file against tags/branches. Apparently someone who has no understanding of svn tagging/branching wrote it. Eclipse and command line are usable. I don't think this should be a show stopper for jbossas, but if say it was for Bill and ejb3 he would need to pull that out of jboss-head (this has to be done at some point anyway). in terms of "being able to develop against the HEAD/Snapshot ..." this would be done on the trunk for all of the mc modules. The issue is what tagged releases need to exist to allow for comparison against those versions. > It would potentially be possible to require the MC projects > to be developed against head while still being thirdparty > binaries in the main jboss-head build. > i.e. You would checkout the projects separately into the head tree. Meaning just dropping them from the jboss-head module alias and manually checking them out into it? If that is the case this should just be done independent of the svn move just to decouple the mc code from jboss5 as currently the only user of these is ejb3 as far as I can see. We just need the mc artifacts pushed out to the repository. > -----Original Message----- > From: Adrian Brock > Sent: Tuesday, May 02, 2006 6:41 AM > To: Scott M Stark > Cc: Adrian Brock; Ryan Campbell; QA; > jboss-development@lists.sourceforge.net > Subject: RE: jboss-head-jdk-matrix Build Failed > > Which of this is the showstopper? > http://jira.jboss.com/jira/browse/JBBUILD-307 > > The issue for me is being able to develop against the > HEAD/Snapshot of each dependent project without creating an > infinite number of versions in the repository. :-) > > e.g. the ongoing integration between AOP/MC require a large > turnaround of changes. > > It would potentially be possible to require the MC projects > to be developed against head while still being thirdparty > binaries in the main jboss-head build. > i.e. You would checkout the projects separately into the head tree. > > This is similar to what is being done with the aop-mc-int, > jca and rars projects until a proper standalone build system > is in place. > > But those are less complication, because they don't have any > main branch integration yet. > ------------------------------------------------------- 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
