On Tue, Mar 26, 2002 at 07:38:16PM +1100, Peter Donald wrote: > Hi, > > Today I had the opportunity to go have a look at a few of the build > management tools. Theres some fantastic stuff going on right now with regards > to this stuff. ... > Anyways they all look like fantastic steps forward. Thus I think we should > eventually move to one of them when they are matured. All of them are way to > dynamic at the moment for using unless we were willing to constantly monitor > them - which would be too big an investment IMHO.
Dunno.. the Turbine projects manage okay, and we've got Maven's inventor here on the list being helpful.. :) > Another problem with each of these products is that they are very monolithic > which makes it difficult to easily take part of the system without the rest > which means they will probably tak a while to mature. Jason posted this a day or two ago: >> If you want to try maven then you can keep run maven along side your >> standard build mechanism. This is what we are doing in Turbine >> because Maven can't yet accommodate all the weird things done in the >> Turbine builds but maven is almost there. So it sounds like you don't need to buy into the whole Maven deal at once. From what I gather, you call Maven's build scripts from your own build.xml. So we could keep everything of our own, and only use Maven's doc system, for example. Not sure if the advantages would outweigh the overhead though. > So what to do in the meantime? Well for the meantime I say we stick with what > we got. We can refactor out some commonalities into top-level build files > (like the jdepend stuff) that don't need to be in each project file. Some > things (like checkstyle) need to be in each projects build.xml so we can > leave them there for the moment. Can't do much factoring out if we want components to be independently buildable :/ ... > Thoughts on any of this? Glad you're keen on the general idea of adopting one of these beasties. I'll keep going with <style> for now. --Jeff > -- > Cheers, > > Pete -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
