Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Common Phing Build Scripts and Tasks for all Doctrine Projects

branch: master
README.md

Doctrine Build Commons

This project is a base submodule for all Doctrine projects that are using a build process yet. It handles versioning, making releases and distributing them.

By the nature of phings limit capabilities we ship a bunch of additional tasks, that mimic Ants API as much as possible to allow future migration to Ant and possibly Manuel Pichlers build-commons library.

New tasks

  • ReplaceTask with options file, token, value
  • VersionIncrementTask with options property and version

Targets

  • Build - Depends on clean, prepare, generate-package
  • Clean - Clearn the directory for the next build
  • Prepare - Retrieve version from Version Class constant, also calculate PEAR version and stability automatically.
  • generate-package - Generates the PEAR package, depends on define-pear-package as "abstract task".
  • pirum-release - Use '-Dproject.pirum_dir=path' during build to push to pirum.
  • distribute-download - Use '-Dproject.download_dir=path' during build to move download file.
  • make-release-commit - This task makes a release commit by asking for the release version, sets composer.json version, the Version constant and then increments the version in the mini level and makes another commit for the next "dev".

Properties

Your build file for a build-common supported project has to look at least:

# Project Name
project.name=DoctrineDBAL

# Version class and file
project.version_class = Doctrine\DBAL\Version
project.version_file = lib/Doctrine/DBAL/Version.php

Usage

Git submodule this repository into your project. Currently has to be at:

lib/vendor/doctrine-build-common

Then add the following into your build.xml:

<import file="${project.basedir}/lib/vendor/doctrine-build-common/packaging.xml" />

Now define the target: define-pear-package. See Common for an example.

Create the build.properties file with the necessary details (see above).

Something went wrong with that request. Please try again.