On Wed, May 14, 2008 at 1:25 AM, Pat Cappelaere <[EMAIL PROTECTED]> wrote: > > Ruote-web and Ruote are the two pieces that might change quite a bit. > So I guess this answers one question: I need to add one more remote entry > in my git config file for ruote itelf to keep it in sync with your changes. > > I may have to make some changes in Ruote to support the upcoming audit trail > analysis API from the Stevens Institute. This could stay in the separate > wfxml branch...
that would call for a fork of Ruote or for a nice bit of monkey-patching from Ruote-web. You're the end user, at the end of the specialization chain, monkey-patching is not bad. > But I cannot assume that the other Rufuses are not changing either... > This gets a little complicated... I need to try a few things to see how this > would work... you can install them as gems (see lib/tasks/install_workflow_engine.rake, second task), even Ruote. Are you building the new GeoBPMS ? Are you building a WfXML-R package based on OpenWFEru ? What's your audience ? Cheers, -- John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
