Marijn Huizendveld wrote: > > On Feb 3, 2009, at 5:42 PM, Jacob Coby wrote: > >> On Feb 3, 2009, at 11:30 AM, Nicolas Perriault wrote: >> >>> 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? ;) >> >> It's not that hard, no. But it has confused literally *every* person >> I know who has used Symfony. Especially on projects that don't keep >> the auto-generated files under source control. "I ran propel-build- >> model like you said but it still doesn't work!" >> >> "Did you run ./symfony clear-cache?" has to be the most common >> response in #symfony as well. >> >> It would be a huge help if build-model and plugin-install both cleared >> the autoload cache (along with any other commands that could introduce >> new files or paths to autoload). I cannot think of any case where you >> would run those commands without wanting to clear the autoload cache.
You are right, but it does not harm either to clear the cache, especially as you are in the dev environment. Fabien > > I think that this is the main reason why it is not (yet) automated. > But still +1 for me > > Marijn > >> I would not want them to do a full "clear-cache" if possible. >> >> -- >> Jacob Coby >> >> >> >> >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
