modules and composer - play together nicer about core

[gnovaro]

See this kohana/kohana#46

[acoulton]

@chrisgo thanks for submitting this.

Kohana 3.3 and all the official modules already fully support installation with composer, and from 3.4 the sample application in kohana/kohana uses composer instead of git submodules to reference the core and all the modules.

By default the modules will be installed to the modules/name path for compatibility, but you can easily force this back to the composer standard locations by adding to your composer.json:

"extra": {
  "installer-paths": {
     "vendor/{$vendor}/{$name}": ["type:kohana-module"]
    }
}

Note that nothing in Kohana actually cares about where the /system or /modules directories are - you can put any module/package anywhere so long as you put the correct path to it in your bootstrap.php.

I'm not sure which Kohana email module you're using - there are a few, and none are official - but the issue with getting a duplicate SwiftMailer is to do with the way they've set up that dependency. It would probably be best to ask them to also publish their module as a composer package and move the swiftmailer dependency into their own composer.json so that it doesn't need to be directly initialised by them.

Alternatively you could just remove the email module you're using and use SwiftMailer directly - in our projects we've found that once you have swiftmailer as a composer package it doesn't really need anything else.