> you would instead end up loading the .wo in your app instead of the
> framework version = complete disaster)
Doh! I've done that before. It can be a real bugger to debugger. :-P
____________________________________________________________________
Brendan Duddridge | CTO | 403-277-5591 x24 | brenda..lickspace.com
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
On Apr 24, 2007, at 2:10 PM, Mike Schrag wrote:
>> That said, the loophole could easily be closed by touching every
>> file in the build directory. That makes deployment less efficient,
>> but also makes it a bit harder to shoot yourself in the foot.
> The better way would be to delete the entire dist folder on a
> deploy. The problem is that you can also end up with old .wo's.
> For instance, if you refactor=>rename a wo, you will still have the
> old wo name in your folder. It's possible to screw yourself under
> certain circumstances (say you moved a wo from the app to a
> framework -- you would instead end up loading the .wo in your app
> instead of the framework version = complete disaster).
>
>> zak.
>>
>> p.s. Incidentally, this kind of problem is why I deploy to
>> versioned directories and then have my apps use un-versioned
>> symlinks pointing to a versioned directory. For example,
> This would work too ...
>
> ms
>
>
This archive was generated by hypermail 2.0.0 : Tue Apr 24 2007 - 17:05:22 EDT