My latest try was vindico, an ant-based gump. I got far enough to see things building and so on, but not far enough to do the project.xml override/inheritance. I do believe it was a viable model, the biggest issue being that I was still using java products to build java products, and Sam had warned me about these types of things. I only stopped because Adam had started pushing more and more code into Gumpy, and I liked the idea of using non-Java to build Java. That, and he was coding much more than I was :)
In short, there are a couple of gotchas with an ant-based gump, but I think it is completly doable. My other ambitions with vindico were more what we are talking about today: doing history on all builds, trying to find who to blame (usually 1 side of a 2-sided interface), moving more toward some type of continuous integration, federation of gumps (so that I am only building 4 projects), etc.
I think that gump should *NOT* try to reinvent the wheel and simply make sense of what the projects already do.
Keep in mind that gump is currently a top level project and we aim at building *EVERYTHING* the ASF does, including HTTPD.
Maybe I am misunderstanding what you are saying or vice versa, but I am in favor of sticking with Gumpy, and expanding it to include anything that can be built, including C code.
Scott
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
