The plan so far has been to roll out jbossbuild to each component under jboss-head. I'd like to propose a change to this plan so that once we do complete the rollout to all components, we can be confident that the other pieces besides jbossbuild will work like we want.
We need to take the implementation of the new build system, project structure, and build repository full circle for one component. This will implement/prove the following functionality: - automated builds published to a build repository (snapshots) - thirdparty dependencies downloaded from the build repository - performing a standalone build of a component which depends on a snapshot component Let's take aop as the initial use case because of it is only dependent on jboss-common. When this work is complete, you sholud be able to: | cd $WORK | cvs co jboss-aop | cd jboss-aop | ant -f jbossbuild.xml synchronize | ant -f jbossbuild.xml build | The synchronize target will download the thirdparty jars & a snapshot of jboss-common. The build target will build the standalone release of jboss-aop. This should give us a concrete basis for moving forward with jbossbuild and the over all restructuring of the build. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865727#3865727 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865727 ------------------------------------------------------- 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
