gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Chalko <>
Subject Re: Cascading Gumps ( was Re: Distributed Gumps )
Date Fri, 21 Nov 2003 19:40:37 GMT
Excelent Idea.  I thnik this could really increase the number of 
indepent gumps.

Adam R. B. Jack wrote:

>Ok, adding SVN (repository with type='svn' as opposed to type='cvs') made me
>realize we could add a repository with type='jars'. Such a repository would
>be a structured jars repository (e.g.
>perhaps produced by an upstream Gump.
>The module descript could have a <jars element, just like we have <cvs and
><svn today, and could give the information needed in order to download the
>[latest] jars from that repository. Once downloaded a module could be deamed
>'packaged' if all it's projects outputs were then found on the disk.
>Having this approach seems to fit quite nicely with what exists inside Gump
>today, and seems easy to code. Bascially it does restrict each module to
>'coming from a known repository' (not any group of repositories upstream)
>but that is livable, maybe better. It does meant the workspace/module
>metadata needs to be modified (kinda like with packages today) but I think
>that a few trailing entries (like next), like we do for packages, are not
>too painful:
>    <module name='abc' jars='repository1'>
>To unsubscribe, e-mail:
>For additional commands, e-mail:

View raw message