A set of php scripts and other files to help in the "build process" of eZ Publish Community Project tarballs and deliverables
The build process carried out by this tool consists broadly speaking of the following steps:
This software is licensed under the GNU General Public License v2.0 . The complete license agreement is included in the LICENSE file. For more information or questions please contact info@ez.no
Read the INSTALL file to get started and for usage instructions
Let's call ROOT_DIR the directory where you will be running the build script. ::
ROOT_DIR/ | ___classes/ php classes with the bulk of the business logic for this tool | ___doc/ more documentation, such as changelogs, todos and known bugs | ___vendor/ where composer will install required php libraries | ___INSTALL installation instructions | ___LICENSE license file | ___README this file | ___composer.json configuration file for composer |
---|---|---|---|---|---|---|---|
___build | |||||||
___source/ a copy of the eZP sources will be downloaded here during the build | |||||||
`___release/ tarballs produced by the Jenkins build will be downloaded here | |||||||
`___apidocs/ where the generated documentation is stored, in a subfolder for each different tool used | |||||||
___dist/ tarballs produced by the build will be made available here | |||||||
___pake/ | |||||||
___ | |||||||
`___ | |||||||
___resources/ |___doxyfile_master config. file used for documentation generation via doxygen |___doxygen_piwik_footer.html template file used as footer for documentation generation via doxygen |___samicfg_master.php file used for documentation generation via sami
___wpifiles/ template files used to the generate the wpi package
Can a standalone copy of pake be used with the pakefile instead of the bundled one? Yes: just use a different command line: :: php pake.php build ...
Can I download a complete zip of the tool instead of doing the bootstrap? Yes. Come back later for a list of urls to use ;-)