"pilhuhn" wrote : And the developer should not only be able to check out a source tree, but also be able to *update* the tree without throwing things away and re-checking out some modules. This not only saves bandwidth, but also time.
Yes, that is the purpose of the build definition. If you look at the synchronize method it actually does the following when executed at the top level. 1) Synchronize the main build project (from cvs) 2) Reinvoke ant to pick up any new build.xml downloaded from cvs 3) Do the same for each component (including checking out any new components that may have appeared in the build definition) With the current JBoss build, any new modules or thirdparty jars requires the developer to look at CVSROOT/modules then go to the relevent directory and do a "cvs co" or blow away the whole thing and check out from scratch. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860774#3860774 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860774 ------------------------------------------------------- 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
