A basic critique (broad brush stuff) PROS of this approach:
1) It is very declartive (though not very human readable) 2) The inputs and outputs are clearly defined and readily available to tools 3) The links between the components/artifacts are clearly defined (you can see what includes what) 4) The declaritive approach makes the build easy to validate 5) The build files are very small and simple CONS of this approach 1) It has the same problem as buildmagic in that the process of the build is obfuscated (although I believe the notions involved can be easily learnt) 2) The idea of an integration build doesn't sit well with the components also being a standalone project (they directly include the integeration project) | <project name="project" | default="build" | basedir="." | > | <!-- The main build --> | <import file="../JBossAS/build.xml"/> | 3) The ant typedef has some limitations which I have been able to workaround 4) Internally it generates ant macros from the typedefs. This is not well defined in the ant documentation and I may have fallen foul of an undocmented feature. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860515#3860515 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860515 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
