Investigate the option of using composer.json as a build file, as an alternative to drush make.

Comments

jp.stacey’s picture

Title: Use composer instead of make » Use composer as alternative to make
Priority: Minor » Major
Issue summary: View changes
jp.stacey’s picture

Status: Active » Needs work

Got a basic build working using a basic (example) composer.json; single unit test working but it does need more testing (check that the sites/all/modules/views folder exists, for example.)

It could also extend GoodBuildTest and just check all the symlinks etc. Or even ReBuildTest. Or both, in two separate test files!

jp.stacey’s picture

Also note that ComposerBuildTest seems to interfere with the other build tests (do they share folders?) so that needs fixing. All test files pass, in isolation only.

jp.stacey’s picture

Status: Needs work » Fixed

Woohoo! This is implemented on 7.x-1.x-dev in fb55dbce0982d9577e2cbe0bca9a6b2f7158e52d as follows:

* composer.json now available on separate examples branch
* Build process abstracted out into classes, brought in using Drush engines
* Errors during build use exceptions
* GoodBuild and ReBuild tests abstracted out, so the same tests are run on both Composer and Make builds to ensure they both work as expected.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.