My first phing buildscript

Because I get more and more components from version management tools it gets harder and harder to move from development to staging level. SVN repositories are the worst offenders, certainly if you see how clean the get and mercurial repositories are.

If you clone or checkout a repository most of the time it also includes test files, build files, and so on. It's stuff you don't need for your application.
Swiftmailer for example comes with a full blown test suite. What if hackers find a way to use it to their advantage?

The phing installation via pear is painless.

The way to delete a directory didn't appear in any of the searches i did. So i moved on to the documentation and I found what i needed.

	<?xml version="1.0" encoding="UTF-8"?>
	<project name="FooBar" default="dist">
	<copy todir="c:\FooBarStage\vendor\swiftmailer">
	<fileset dir=".\vendor\swiftmailer">
	<exclude name=".git\**" /> <!-- exclude .git directory files because they can be locked -->
	<exclude name=".gitignore" />
	<exclude name="CHANGES" />
	<exclude name="README" />
	<exclude name="README.git" />
	<exclude name="VERSION" />
	<exclude name="build.xml" />
	<exclude name="create_pear_package.php" />
	<exclude name="package.xml.tpl" />
	</fileset>
	</copy>
	<delete dir="c:\FooBarStage\vendor\swiftmailer\.git" />
	<delete dir="c:\FooBarStage\vendor\swiftmailer\doc" />
	<delete dir="c:\FooBarStage\vendor\swiftmailer\notes" />
	<delete dir="c:\FooBarStage\vendor\swiftmailer\test-suite" />
	<delete dir="c:\FooBarStage\vendor\swiftmailer\tests" />
	</project>

view raw gistfile1.xml hosted with ❤ by GitHub

It's not very elegant but i'm taking babysteps at the moment.