TODO: This should be replaced with tasks in JIRA 1) Do the other projects within jboss-head - this is an alternate build for now, i.e. you have to do ant -f jbossbuild.xml This basically involves copying common/jbossbuild.xml to the other projects and updating it. It will also involve specifiy those components in jbossas/jbossbuild.xml along with adding references to thirdparty jars
2) Some things are missing from the targetdefs at time of writing: build.bin - processing for src/bin build.resources - processing for src/resources rmic, javacc, aopc compilation sar/war/ejb target builds docbook build (needs including in the overall doc target) I also haven't tested the notion of a file being an artifact, e.g. jbossjca-service.xml 3) Need to externalize the filesets for normal ant targets. The pseudo <filesets/> is not available there. e.g. make the following | <source id="main"> | <include input="commons"/> | <include input="concurrent"/> | <include input="dom4j"/> | <include input="jaxme"/> | <include input="log4j"/> | <include input="regexp"/> | <include input="slide"/> | <include input="wutka"/> | <include input="xerces"/> | </source> | generate a main.filesets, main.sourcepaths, etc., that can be referenced in the normal fashion 4) Need to build the binary versioned repository (currently it is just using thirdparty as checked from cvs). This will enable developers to only checkout and build those components. 5) Need to complete the cvs checkout processing so it takes into account user ids in the path and passwords for those without sshd. Also need to allow developers to specify what source they want to work on and want can just be binary download from last nights build. This will probably be best implemented using a local.properties file in jbossas 6) Beyond (5) we then need to do the work for developing standalone projects alongside each other. e.g. 1) Allow the cache project to override the binary downloaded into thirdparty with their local source project e.g. 2) Allow the Seams/Portal projects to include a binary build of JBossAS which they can then deploy to rather than it being a multistage checkout/build process View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862655#3862655 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862655 ------------------------------------------------------- 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
