On 7/21/07, Tammo van Lessen <[EMAIL PROTECTED]> wrote:
2007/7/21, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > I like having an example extension module, and there are other possibilities for examples. The pitfall is dependency creep, but we can do that case by case. Yes, but at first only during build time - There should be also some kind of README file that explains "if you use this, you'll need that dependencies"... > We could call it "ode-commons"... :) :) What about "ode-extensions"? I'm still having the extensionActivity/extensionAssignOperation implementation in my queue, so we could use this module also for upcomming extensionActivity implementations...
I'd go for for just "extensions" (we know already we're in ODE right?). We're going to have other commons, for example this annoying bpel-epr that should really be renamed iapi-common once the BART branch is merged. Matthieu Cheers,
Tammo -- Tammo van Lessen - [EMAIL PROTECTED] - http://www.taval.de
