Sam Ruby <[EMAIL PROTECTED]> wrote on 02/01/2003 02:22:37 PM: > [EMAIL PROTECTED] wrote: > > > > Answering my own question: the profile 'extends' a project by adding a
> > 'package' which is actually the directory in the 'pkgdir' of the > > 'workspace'. > > > > Clear as mud. > > Sigh. This was done in an attempt to appease an individual who > apparently could not be appeased. I'm just frustrated. Don't let it get to you. I try not to :-) I'm also trying to update docs/code as I find things that are hard to understand and use. For example, the web site says to use gump, you run gen, update and build. But what's not clear is when you would want to re-run them, and what they produce. e.g. Why would I want to re-run gen? What's the relationship with the gen target in build.xml? etc.... Frustration often gets fixed.... > For now, lets focus on the fact that in the last few days you have > become aware of a number of integration issues that you otherwise would > not have been aware of without gump. If we can build upon that, we can > truly have an early warning and feedback cycle between all projects. Yep. And I'm happy that it can be done. > Let me be quite clear: I don't care if every last shred of code and/or > data in Gump is replaced. What I do care is that there is some > mechanism to do a complete and clean bootstrap from source of every ASF > java component, and when there is cross dependencies between such > components, that the version of such dependencies used in the complation > process is either the HEAD or a tagged version of such dependencies that > have themselves been built in this way. Does this mean projects like James who have had failing gump builds because of changes in dependencies, can specify a version of a gump built jar to use until the problem is resolved? -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
