Phing is a PHP port of Java Ant. It is a great tool to use in development. It standardizes a lot of build scripts you would have to maintain internally. Unfortunately, examples seem to be lacking. As a quick introduction to Phing, I will show how you can check all your php scripts for syntax errors.
If you have never heard of Phing before, I suggest you visit the getting started page.
The phplint task will syntax check one or more files containing php source code. All it requires is a list of files.
Here is the sample build.xml file:
We created a target called "lint". This will allow us to call lint from the command line. In that target we specify a single task: phplint. The phplint task will call "php -l" on each filename provided. Within that task we specify a fileset type. The fileset type is what provides the phplint task with files to syntax check.
The fileset type can get pretty complex. I have intentionally kept it simple. The dir attribute on the fileset type specifies the current directory. The first include element will match any file with a ".php" extension in the current directory. The second include element will match any file with a ".php" extension in a sub-directory.
Here is a visualization of how the fileset is working:
build.xml <-- will not match
foo.php <-- will match
bar.php <-- will match
baz.php <-- will match
special1.php <-- will match
special2.inc <-- will not match
schema.sql <-- will not match
Place the build.xml file at the root of your applications directory structure. You can move it to another folder after you get more comfortable with phing.
From the command line run: phing lint