From: Scott M S. <sco...@at...> - 2003-05-21 17:12:48
|
There is no confusion about what bm is. My mandate is that there is justification for using it over Ant alone. BM is not simple standalone tasks that can just be used by throwing in a taskdef. There is a requirement to have dependencies on hidden bm targets like _buildmagic:init. Could be just inadquately doced, poor use of names, overdesigned, etc. At this point I want justification as to why I need the bm tasks and why And yes, bm is broken. In the 3.0 branch I cannot run a 'build.sh clean most' command from the jboss-3.0/build directory. The same problem existed in 3.2 until I backported the head bm code and xml fragments, at which point the module property was not getting propagated correctly. There are also these supurious msgs now showing up that do not in 3.0: _buildmagic:init: Trying to override old definition of task libraryset Trying to override old definition of task execmodules Trying to override old definition of task resolveproperties Trying to override old definition of task resolver Trying to override old definition of task require Trying to override old definition of task _dump Trying to override old definition of task _puke Trying to override old definition of task moduleinit Trying to override old definition of task moduleconfig Trying to override old definition of task modulelibrary Trying to override old definition of task projectinfo Trying to override old definition of task library Trying to override old definition of task Ant Trying to override old definition of task moduleinfo Trying to override old definition of task projecthelp Trying to override old definition of task propertyfilter Trying to override old definition of task call Trying to override old definition of task property So, in short, I think the build system is too complex because of the obfuscation on top of Ant and this needs to be addressed. I want to see what bm is saving me over straight Ant and I want previously hidden tasks(still are in 3.0) located in *.ent documented. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jason Dillon" <ja...@jb...> To: <jbo...@li...> Sent: Wednesday, May 21, 2003 12:02 AM Subject: Re: [JBoss-dev] Why go forward with buildmagic? > On Wednesday, May 21, 2003, at 07:28 AM, Scott M Stark wrote: > > > Which is why the question was posed as "Why go forward with > > buildmagic?", not > > "How do I fix buildmagic to work with Ant 1.5.3?" Stripping bm down to > > the > > minimal essentials as suggested by Jason to run would be good, but I > > don't think > > its worth keeping this wrapper layer at all. Demonstrate why Ant will > > not work > > before discussing why I need a leaner bm. > > I thought I had answered this question last night, but I will try > again. First I gotta stress that BM is a set of tasks for Ant and not > a replacement for it. I was under the impression by reading the Ant > manual that writing custom tasks was how you added extra functionality > to Ant... so why all the fuss about the BM tasks and why all the > confusion about what BM is and is not? > > The core functionality which the BM tasks provide which the core Ant > tasks do not is the ability to execute a dynamic set of sub-projects > and collect the output based on a set of rules. > > That does not mean you can not do the same thing with core Ant though. > It is possible to have a string of ant & antcall tasks which produce > the same basic effect. Actually that is all that the executemodules > task really does, just that it does so with less XML & allows simple > group based selection of which modules to execute. > > It should also be possible to achieve the same effect as executemodules > from a script or jellyscript task. The only difference there is that > the code is in the XML instead of in a .class, which could help with > portability across new ant versions in some ways. > > * * * > > Can you or someone else please explain to me what the real complication > is here? What precisely is too complex about the BM tasks? What > precisely is too complicated about the JBoss build system? > > I get so much "The build system is too complicated" and not enough > explanations of why they have come to that conclusion. > > --jason |