*finally* starting to play with sevak... I see that the SevakTest block
is essentially a "deployer" service. Any objections to moving this out
of (or creating a copy) the test folder into the main source tree?
I see a block that can be easily subclassed and have its service()
method overridden with additional dependencies..
-pete
--
peter royal -> [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- Re: [sevak] creating a "deployer" block Peter Royal
- Re: [sevak] creating a "deployer" block Greg Steuck
- Re: [sevak] creating a "deployer" block Ulrich Mayring