> On Thu, Sep 17, 2009 at 9:14 AM, Jordan Ritter <[email protected]> 
> wrote:
>>
>> What I'm trying to say is that in current ruote2.0 there are services that
>> rely on "work" existing but don't create the directory if it doesn't exist,
>> thus throwing an exception.  Manual effort is required on my part for Ruote
>> to function without the wfidgenerator (mkdir from shell, or FileUtils.mkdir
>> from in my code).
>> If I understand you correctly, you're saying that the services
>> shouldn't trust each other for things like pre-existing directories, but I'm
>> trying to point out that they currently do, and was additionally suggesting
>> a DRY solution (FsStorageEngine init mkdir's workdir) over the non-DRY
>> check-for-workdir-in-every-single-build_service-statement.  I understand
>> that it's outside the engine's job, but AFAICT that's the quickest DRY way
>> to fix this.
>>
>> Observe my ruote server with overridden wfidgenerator and no work directory:
>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/fileutils.rb:1032:in
>> `initialize': No such file or directory - work/tracker.ruote (Errno::ENOENT)

Hello Jordan,

thanks for the feedback and the suggestion. It's in

  
http://github.com/jmettraux/ruote/commit/dcab926c4f0e39b87b595f65d8b7bbd4f320a0be


Cheers,

-- 
John Mettraux   -   http://jmettraux.wordpress.com

--~--~---------~--~----~------------~-------~--~----~
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to