gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gene...@gump.apache.org
Subject [Gump Wiki] Updated: GumpCode
Date Mon, 12 Jul 2004 19:31:11 GMT
   Date: 2004-07-12T12:31:11
   Editor: 67.235.113.203 <>
   Wiki: Gump Wiki
   Page: GumpCode
   URL: http://wiki.apache.org/gump/GumpCode

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -23,6 +23,8 @@
 
 The [http://brutus.apache.org/gump/pydoc/gump.runner.html Runner] loops throug the build
sequence and (when needed) does an [http://brutus.apache.org/gump/pydoc/gump.update.html update]
on a module before doing a [http://brutus.apache.org/gump/pydoc/gump.build.html build] of
the project. When done (with each) a [http://brutus.apache.org/gump/pydoc/gump.core.gumprun.html#RunEvent
Run Event] is dispatched to all listening worker/actors. The workers/actors do their thing
(e.g. update stats, generate documentation, etc.)
 
+Note: Currently context (such as output from exec commands) are stored on the model, not
on a wrapper, hence the module is poluted by the run & not re-usable. [Work todo...]
+
 '''Workers (Actors)''':
 
 The workers work on the content tree (the tree of results) based off events that come from
the runner, e.g. module complete, project completed, etc. These actors process the state of
the entity and do their thing (including updating information on that entity in the tree,
e.g. timestamps).

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message