I know that I originally wanted all builds to be standalone, but working with your impl has made me feel differently :-)
The main reason I see to keep project (component) builds dependent on a toplevel build is because the toplevel build is repsonsible for defining the versions of all components. | <include project="common"> | The above defines a dependency on common, but doesn't specify which version. Even if we were to structure the repository as you suggest-- essentially have the repository structure implicitly represent required component versions, you would still need to specify the repsitory root, ie, repository.jboss.com/jbossAS/4.0/ which again ties you to an integration project. I suppose each component could define the version for each of its dependencies, but I don't think this is scalable. What if each component simply referenced the toplevel build as: | <import file="../build/release.xml"/> | And then each workspace would be structured (and potentially reconfigured by the developer) to support this convention. This would preserve the simplicity of the existing structure and would acheive the decoupling of the component builds from a specific release build. The aop-standalone prototype (coming next) will follow this convention. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867281#3867281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867281 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
