http://dev.koseven.dev/ http://dev.koseven.dev/favicon.ico?1392677580 2014-08-28T01:52:12Z KO7 Development Redmine http://dev.koseven.dev/issues/4839 2014-08-28T01:52:12Z Guillaume Poirier-Morency guillaumepoiriermorency@gmail.com <p>I have a prototype here <a class="external" href="https://github.com/arteymix/ko7-makefile">https://github.com/arteymix/ko7-makefile</a></p> <p>The tool is very useful for settings permissions and running tests.</p> <p>I think we should consider having a good make tool in the sample application for the 3.4.*.</p> http://dev.koseven.dev/issues/4782#change-17279 2014-08-28T01:44:26Z Guillaume Poirier-Morency guillaumepoiriermorency@gmail.com <p>Moving to composer is a nice idea. This will allow KO7 modules to define a wide range of dependencies.</p> <p>Although, I think that modules designed specifically for KO7 should end in modules and external libraries in application/vendor. This makes a clear dinsinction between what gets autoloaded by the CFS and what gets loaded by composer. Technically, we add "vendor-dir": "application/vendor" in "config" in composer.json.</p> <p>Then, only add a line after the modules loading in bootstrap.php</p> <pre> // Autoloading composer packages require KO7::find_file('vendor', 'autoload'); </pre> <p>This is pretty much what I do right now. This doesn't break anything and allow a full access to composer.</p>