RE: Centipede & multiple projects

	The problem with the current multi-project-in-module approach is that it
	uses only one centibuild file, which *starts* the process. Hence even if
	we make the multiproject system get the right buildfile, we still need
	to tell centipede which buildfile to start with, and which project.
	Bleah. :-P

The gump descriptor (i.e. each project within the module.xml) can tell
centipede which buildfile to use.

	So real multiproject builds should be done with Gump, that's all. What
	we have now is a short-circuit that works for one centibuild file and in
	the same module.

I agree, I want to. I don't know if a "how" is on the horizon though...

	It's becoming IMHO more evident that the best thing, as we said some
	days ago, is to zap it and use an external system to drive multiproject
	builds.

I am trying. I have something (gump) that knows which project is which, but
no way to get that into centipede.

	If we want we can still do it with the code we have, with a new cent
	script that calls that code, but the best thing is to use Gump and
	that's all.

I am ok to accept an "ugly" solution whilst cents become ant taglibs or
whatever, but I don't want to wait. I think that using centipede in gump
(and seeing it get daily usage) is a motivation for centipede developers to
take on that next phase. I see a sort of chicken and egg here...

If I can not use centipede I will be forced to manually build lots of ant
scripts. I love ant, I hate writing repetitive complex scripts, blurgh...

regards

Adam



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf