Hi Ryan, I don't anticipate that all builds will be standalone.
And certainly developers won't want 20-50 standalone projects that they have to build separately, update the jars to some location then build the next until you get a final project. The idea of the build is that the developer can checkout the projects they want to work on. Where they aren't going to modify a project (or use a project under development) they can just download the binary into thirdparty. The projects they do want to work on, can be checked out from cvs as source components. For the nightly builds, cruise control could checkout all the projects as source and rebuild the whole thing in one go. In this example, the project is using the jboss-common.jar as a binary but test1 and test2 are under development. If I were to develop it further, I would add a local properties file where the developer could specify which elements of the project they want as binary and which they want the source/latest development version. The default being as now (all components checked out as source). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860651#3860651 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860651 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
