I have completed the prototype of the aop standalone build. The functionality is equivalent to that originally described, but some things have changed.
Here is how to create the build: cvs co -d aop jboss-aop | cvs co tools | cvs co -d build tools/etc/jbossbuild/release.xml This will give you the following directory structure: aop | build | tools release.xml should be elsewhere, perhaps in its own module. At any rate, once you have the above checked out, you can call cd build | ant -f release.xml synchronize.components This will download the jars from the repository and put them in thirdparty. This is currently located at http://cruisecontrol.jboss.com/repository. Cruisecontrol is setup to run the jbossas/build.xml daily, publish the binaries, and email me: http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-repository You can then ant -f release.xml build And the release structure for aop will be built: ./output/jboss-aop-1.0.0-FINAL/lib/concurrent.jar | ./output/jboss-aop-1.0.0-FINAL/lib/javassist.jar | ./output/jboss-aop-1.0.0-FINAL/lib/jboss-aop.jar | ./output/jboss-aop-1.0.0-FINAL/lib/jboss-common.jar | ./output/jboss-aop-1.0.0-FINAL/lib/junit.jar | ./output/jboss-aop-1.0.0-FINAL/lib/qdox.jar | ./output/jboss-aop-1.0.0-FINAL/lib/trove.jar I'll followup next with some discussion on limitiations, improvements, etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867316#3867316 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867316 ------------------------------------------------------- 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
