Sam Ruby wrote:
> Proposed option: parallel copy operations:
>
> [SNIP]
>
> This change could bring Nagoya back to parity with a Pentium.
LOL
> Catastrophic dependency failure insurance:
>
> Suggestion from Geir Magnusson Jr: if at the completion of every
> successful build, the output jars are copied to a well defined location
> and then this location is used as the source for resolving dependencies,
> then we have a system that automatically upgrades. I kinda like this
> idea, and am curious what other people think...
>
> This discussion was motivated by yesterday's xml-xerces build failure...
I like this idea too :)
>
> Defining a few terms:
>
> I think of gump as a PROFILE. A set of PROJECTs and TAGs that at least
> one person sees as an interesting configuration. The proposal
> directory, contains a codebase which while fun to write and useful at
> the moment, I view as totally expendable. Hopefully other people will
> someday define other profiles of interesting configurations.
>
> I see a WORKSPACE as corresponding to a physical set of files on your
> hard drive. Hopefully in the future, the definition of a workspace can
> be produced by combining and subsetting profiles, as well as adding in
> additional projects.
>
> I see a build TARGET as something you reference to specify what you want
> built. At the moment, only projects and a special target named "all"
> are defined, but it would be nice if you could define your own subsets
Yes - and it would be nice to add a 'reference workspace' - (not sure if
this integrates with your definitions...) - the idea is that I would
like to add to the Gump Central Services nightly run arbitrary things
for it to do, where the definition for which is located in my
(Velocity's) CVS. So I can add little bits when I need something (like
adding something ephemeral, like gumping a release candidate...) and
remove them, w/o having to touch the central gump workspace.
It also means that each project could take advange of gump's services
w/o needing karma for gump's CVS.
I imagine in implementation that it would be an element of a workspace
that pointed to a workspace definition in a CVS somewhere else. I will
try and sketch out what I am thinking about...
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
