I'm guessing you perform a `composer.phar install --optimize-autoloader`, `composer.phar dump-autoload --optimize`, or something similar?
If so, then I suggest you _don't_ optimize the autoloader in development. Composer won't create a class-map, but will use it's default PSR-1 / PSR-4 dynamic autoloader, which will always find new classes. A class-map will speed up autoloading slightly, so it's a good idea on non-development environments, but as you've noticed it's not convenient in development. -- Jasper N. Brouwer (@jaspernbrouwer) On 3 November 2014 at 20:30:17, Antenne ([email protected]) wrote: > Hi Jasper, > > thanks a million, indeed it is a classloading issue, I regerated my > autoload classmap and that fixed the issue. > Is there an easier way to deal with this? Now I have to regenerate my > classmap every time I add a model class. > > Thanks!! -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
