One final issue that springs to mind is how to handle tools, thirdparty and branching.
Essentially what I have to do with the current build is: 1) Define an alias that incorporates all the components that make up checkout 2) Create a "build" project so I can override the groups definition of buildmagic, this could also be done by creating a branch within JBossAS build 3) Define an alias for the thirdparty jars I want 4) Modify tools if I want to include new projects/thirdparty - I cannot remove unused stuff unless I create a branch in the tools module The downside of using a Branch for the pojo project is that modifications need to merged across yet another branch (it is already becoming unmanageable with three active branches). As a positive though, I don't need to create a system2 or jmx2 since I can work in the branch and merge the changes later back into the main line. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860670#3860670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860670 ------------------------------------------------------- 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
