Classes not showing up in composer classmap

[bramstroker]

Hi Jurian,

When I use composer dump-autoload --optimize to generate a classmap the Soflomo\Log classes are not listed.
I have debugged using the composer source and found out that the path starting at the src\ folder is not respecting the PSR-0 rules. Composer matches the path against a certain regexp before adding it to the classmap. ({C:/www/myproject/vendor/soflomo/log/src/Soflomo/Log.+(?<!(?<!/)Test.php)$}). So the lib should be on src\Solflomo\Log instead of src\Log
This seems to be a problem with all your modules published in the Soflomo namespace.

Bram

[juriansluiman]

Hi Bram,

In our case the class files are loadable by composer. The Module.php does not follow the PSR-0 and therefore it's listed inside the classmap. The other class files inside src/ are "semi" PSR-0 compatible as the Soflomo\Log namespace maps to src/Log in the psr-0 autoloader.

So if you dump the classmap, it is correct the files under src/ aren't shown. However, in our case (I just double checked with Soflomo\Common) if you install the module via composer you can enable and use the module in your zf2 app.

[bramstroker]

It is working when the namespaced mapping is used as fallback, but we want to load ALL our classes by the classmap autoloader because of performance optimization. For the composer classmap generator to work files need to be 100% PSR-0 compliant.
I'm using several ZF2 modules and the Soflomo\Log module is the only one giving problems.
It's not such a big deal because it are only two files which are not loaded by the classmap, but it would be nice if you could fix it so everything is confirming the standards.

[juriansluiman]

Ah, now I understand your use case.

The point is: I don't like the vendor prefixes in ZF2 modules for corporate modules. That's why I use at Soflomo Soflomo as module name. The src directory gets too deeply nested with those two levels, so I found out how the ZF2 autoloader and composer autoloader could work with this setup. But I haven't thought of your use case.

I'll get back to this, so I keep the issue open, because it also affects all other Soflomo* modules.

[bramstroker]

Thanks for your quick replies Jurian!
I also don't like the ZF2 way to namespace your modules i.e. MyVendorMyModule instead of MyVendor\MyModule. At our coorporation we use the first flavour because 99% of the modules does it that way. If you choose the second flavour (like in your case) what's the big disadvantage of an extra nesting level in your directory structure? When using a good IDE (ie phpstorm) it would be quite trivial to browse to your source files / find usages etc.

[anji4]

Fatal error: Uncaught exception 'Zend\ModuleManager\Exception\RuntimeException' with message 'Module (Log) could not be initialized.' in C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\ModuleManager\ModuleManager.php:140 Stack trace: #0 C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\ModuleManager\ModuleManager.php(81): Zend\ModuleManager\ModuleManager->loadModule('Log') #1 [internal function]: Zend\ModuleManager\ModuleManager->onLoadModules(Object(Zend\ModuleManager\ModuleEvent)) #2 C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\EventManager\EventManager.php(460): call_user_func(Array, Object(Zend\ModuleManager\ModuleEvent)) #3 C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\EventManager\EventManager.php(204): Zend\EventManager\EventManager->triggerListeners('loadModules', Object(Zend\ModuleManager\ModuleEvent), NULL) #4 C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\ModuleManager\ModuleManager.php(100): Zend\EventM in C:\xampp\htdocs\Anji\vendor\zendframework\zendframework\library\Zend\ModuleManager\ModuleManager.php on line 140