I have a standalone build of AOP that works like this. build.properties <- desginates the main (toplevel) build for this workspace tools/* aop/ release.xml <- contains toplevel build for aop jbossbuild.xml <- contains componentdef for aop thirdparty/ <-- working on getting this from repository
So, in this setup, aop/jbossbuild.xml uses a property from build.properties to determine where the main build is. If it can't find this file, it defaults to jbossas. So to build the release, you would do ant -f release.xml build Two issues I can see thus far: 1. Using build.properties in the root of the work dir is a hassle and won't work long term, unless perhaps we create a cvs module which contains this and aop & tools. Not sure we want more fun with modules. What is a better way for a component to know which main build to use? 2. Having the aop main build in the same directory as the aop componentdef (jbossbuild.xml) doesn't seem to jive well with the synchronize target which wants to update the main build & then the components which results in aop being update twice. I think I can work around this, but perhaps there are other good reasons to have main builds be in seperate directories? I am ignoring these issues for the moment while I implement the cruisecontrol build & publish task, but I wanted to get them out here. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866830#3866830 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866830 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
