Erik Hatcher wrote: > > I don't quite have the bandwidth to fiddle with Gump beyond what I've > already done with it, unfortunately. I was able to get my own project > building with it, but basically bypassed all the dependency information > first to ensure Gump was building my project successfully. Now I need to go > back and modify the configuration to build the HEAD version of Ant so that > my project then builds from a freshly built version of Ant, and then keep > pushing back dependencies from there until my project is running complete > from HEAD versions of all its dependencies. > > The trouble is that its taken me some time to wrap my head around Gump's > configuration files and how it works, and then its tricky (not difficult > though) to adjust the process in phases so that I slowly ease into building > it all from HEAD - but doing it all initially is too much for me to tackle > at once.
Why do it all at once? Take a look at the latest gump build. I'm sure in two minutes you can spot three things that can make the build get a little further. Submit them, and check back in six hours, or tomorrow, or the middle of next week. I'm not suggesting any paricular time schedule, but just think - if you just average one change a day, imagine what you could accomplish in a month. I personally find this very rewarding. I get to discover new projects that I would never have heard of before. I get insight into the personallities of the developers and the communities. I see problems that would have otherwise gone undetected. In most cases, people are appreciative of this input. Don't worry about wasting CPU cycles on these machines. They would otherwise be wasted anyway. Or in having red show up on the page. Any red lines that appear will be in plenty of company. Try it for a little while. You will learn much about Gump, the code bases, and the communities behind these code bases. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
