ephigenia / phing-tasks Goto Github PK

It’s not possible to use different deployment methods (rsync, ftp) within a project. Therefore it would be great to have an extra environment dependent variable to set the deployment method to use.

Concerning the git.xml I had either to clone the super project recursive or use my own build task to test for git and pull it using `git submodule --init [--recursive] update".

Making the git.xml less useful by the time it is installed.

A short readme section on how to (easily) use phing-tasks with git hosted projects and phing would be nice.

What might be even faster to deploy is a composer.json (registered with packagist.org). That way all my build script needs to do is testing for composer and executing composer install.

Since I seem to have to much free time I could provide (and register) a composer.json if you like.

Replace wget with curl or something that is available on linux and osx systems when downloading yui compressor for js.

Make it possible to define the assets.js.files as a FileSet instead of have a very long csv list of files in the build.properties file.

Since 1.6.6. of git you can git submodule --init --recursive update. That way you no longer need to init explicitly nor utilise the foreach.

Can't tell if --recursive is helpful or might be unwanted for any other use case. In some cases it was helpful (like doctrine integration). Maybe a separate submodules-update-recursive would be the better choice. It wont effect repositories without submodules thought.