On Tue, Feb 3, 2009 at 5:27 PM, Tom Boutell <[email protected]> wrote:
> Subject line says it all. There is no situation in which leaving the > cache uncleared after one of the above operations makes sense. It's > tedious and accident-prone... why not automate it? Perhaps because typing ./symfony propel:build-all && ./symfony cc is not that hard? ;) But I agree, each time new classes are generated, the autoloading cache should be always regenerated automatically. ++ -- Nicolas Perriault Training and Consulting Manager at Sensio Labs http://prendreuncafe.com - http://symfonians.net - http://sensiolabs.com Pro phone: +33 140 99 82 11 Mobile: +33 660 92 08 67 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
