Gump is currently running though the Avalon builds mixed results.
Basically all of the simple builds are working fine but there are a
couple of problems that have emerged:
1. some problems related to inconsistencies between the facilities
index and content
2. plugin dependencies are not being considered when generating the
gump descriptors (causing several component builds to fail due to
non-availability of the meta plugin)
Aside from the above - things seem to be proceeding nicely. Taking care
of the above two items should not be a problem following which we have
the builds of cornerstone which are themselves dependent on the build of
the Excalibur projects. I'm not too sure just at the moment what the
best approach for the Excalibur content - but I'd like to sort something
out so we can move ahead and get James building again (I've got a magic
based build of james up and running - and passing runtime tests) from
which we can validate the updates to cornerstone.
Cheers, Steve.
> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> Sent: 22 August 2004 17:29
> To: Avalon Developers List
> Cc: [EMAIL PROTECTED]
> Subject: more on gump
>
>
> I have just replaced all of the avalon/trunk gump project descriptors
so
> that they now point to svn content as opposed to cvs.
>
> I am expecting some errors related to project id to gump id names
> mappings and will sort these out as they come up. All of the new gump
> project definitions (138 in total) are using magic to build the
> respective targets based on generated definitions - so if something
goes
> wrong we should be updating information in either magic's gump task or
> more probably gump alias declarations in our local index files.
>
> Steve.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
