AppKernel vs. Composer update circular problem

[symvato]

When pulling down committed code that includes both the completed composer.json reference and the bundle's instantiation in AppKernel, running composer update on a new git cloned directory results in:

PHP Fatal error: Class 'Beryllium\CacheBundle\BerylliumCacheBundle' not found in /home/vagrant/CPH/cph-api-services/app/AppKernel.php on line 36
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the post-update-cmd event terminated with an exception

I have tried running composer update and composer install with the --no-scripts options, but this only results in symfony2 not properly installing this bundle.

The main idea of automating this git pull and run with it approach in my case, is so that other people can run my vagrant machine and run one or two commands and be off to the races. With this bundle, I run into a rather big snag. Is there a way I can shell script around the problem or provide the proper instructions?

[beryllium]

I was unable to replicate this issue with version 0.1.2 of CacheBundle on Symfony 2.6.3. The fact that the class isn't found is strange, it sounds like the issue is with Composer or the autoloader - but this was part of my attempt to replicate the issue, as well, and composer seemed to work fine.

[symvato]

Hmm. Either it's not a real issue or perhaps a different problem than I think. Here's what I did, in short:

I installed the bundle, per the instructions and wrote an integration test, which passed. My controllers used the cache and worked well. I committed and pushed via git. No problems. During my commits, I noticed that my vendor/beryllium stuff was going up. I push that up so that my sales type people running the backend vagrant boxes don't need to usually run any composer commands.

On another machine, I git pulled. Initially when running the controllers, those machine's controllers got a class not found concerning a Beryllium class. I don't remember which one. I believe it was during the AppKernel line, so I ran the composer update on the vagrant box. This is when the composer update failed on the AppKernel line, because composer hadn't yet finished. It was, indeed strange. I had to comment out the line in AppKernel first, run composer, then put back the line in AppKernel for the bundle to work.

[symvato]

I've noticed that I'm on Symfony 2.5, so I'm changing mine to 2.6.3 for starters. I'll update this with any results.

[beryllium]

Do you know if the vendor/autoload.php and vendor/composer/* folders also got committed? I usually don't commit the vendors, so there might be some particulars that behave unexpectedly.