phing

I'm doing PHP development and I'm thinking of using one of these. I have both PHP and Java installed on my machine. In theory I could use any of the two. What are the compelling arguments to pick Phing over Ant? The greatest argument I have in favor of Phing is that it's fully developed in PHP ; which means, at least : You can debug it / submit patches if you want You can develop tasks in PHP including tasks which are specific to your project that can use stuff from your project (I've written a couple of tasks that use functions of Drupal, in a drupal-based project) And, if you are working on

I've been reading about Phing and Ant and I'm not sure which, if either, of these tools are most useful for this scenario. It could easily be debug statements etc, but I'll give you our literal scanario. We have a free and premium version of a downloadable PHP app, and rather than including just a variable hidden somewhere and then doing: if($premium == true) { echo 'some additional functionality'; } else { echo 'basic functionality'; } Obviously someone could then take the source and change that variable, and bang - they've stolen our code. And something like Ioncube etc is just totally

I'm trying to use Phing to automate : running tests running DB migrations on each Developer machine [using dbdeply] deployment to production when needed I think it does make sense to add a build folder in my project and put all my build configuration files and db deltas in that folder. and commit all that into the SVN repository. so every developer will get the updated build files when he check-out from svn. and be able to run the build to update his DB with the new changes. on the production server: I was planning to add another build file there to get the latest Tagged version in svn and

After reading the "Modern PHP workflow" article in the November 2008 edition of php|architect magazine which discussed unit testing ( phpUnit ), build tools ( Phing ) and continuous integration ( Xinc ), I'm inspired the learn more about some of the tooling available for PHP, especially Phing. In the past I've often handled deployment to a production server by running the live site as a subversion working copy and simply running an "svn update" on the production box to deploy the latest version of the code. Do you use build tools for PHP code? What advantages you you believe they offer over

As given in https://phpunit.de/manual/current/en/installation.html#installation.phar.verification , the steps to globally install the PHAR are: $ wget https://phar.phpunit.de/phpunit.phar $ chmod +x phpunit.phar $ sudo mv phpunit.phar /usr/local/bin/phpunit $ phpunit --version PHPUnit x.y.z by Sebastian Bergmann and contributors. I followed the above, but with the URL for the older version, i.e. https://phar.phpunit.de/phpunit-old.phar (because our PHP version is older). I ran the following commands then - $ chmod +x phpunit-old.phar $ sudo mv phpunit-old.phar /usr/local/bin/phpunit Note - My

I'm trying to setup a new Continuous Integration server that utilizes Phing and PHPUnit for automatically running test cases. I've installed Phing with Pear: pear channel-discover pear.phing.info pear install phing/phing I've installed PHPUnit using the new PHAR method: wget https://phar.phpunit.de/phpunit.phar chmod +x phpunit.phar mv phpunit.phar /usr/local/bin/phpunit Then I go to the directory where my build.xml file is located, rung phing and it looks like Phing has no idea where PHPUnit is. [jenkins@leroy workspace]$ phing Buildfile: /home/jenkins/.jenkins/jobs/Framework/workspace/build