Download the PHP package vasek-purchart/phing-copy-files-task without Composer
On this page you can find all versions of the php package vasek-purchart/phing-copy-files-task. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download vasek-purchart/phing-copy-files-task
More information about vasek-purchart/phing-copy-files-task
Files in vasek-purchart/phing-copy-files-task
Package phing-copy-files-task
Short Description Copy files with better control over copying than the default Phing CopyTask
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phing-copy-files-task
Phing Copy Files Task
Copy files with better control over copying than the default Phing CopyTask.
The main disadvantage of the default task is that it ignores the overwrite="false" setting (which is also default) and if the source file is newer, it always rewrites the target file (see phingofficial/phing#538). This is unexpected and potentially very dangerous behaviour especially when copying configuration files etc.
CopyFilesTask has much narrower use-cases, but offers you more control about the copied files. It works only with files (not directories or filesets) and you can specify how exactly each of the files should be copied and what to do when the target already exists.
Usage
To copy a file you can just write:
The paths are relative to the location of the buildfile. If you want to use absolute paths, you can write paths using ${project.basedir}, which contains the location of the buildfile.
You can also copy multiple files within one task definition:
Target file exists mode
If the target file already exists, there are three modes how you can choose that the situation will be handled:
1) skip (default) - copying of the file is skipped (and logged to output)
2) replace - always replace target file, even if it exists
3) fail - do not overwrite the target file and fail the build
You can set the mode for all files at once with existsmode parameter on <copy-files>:
And also for each <file>, meaning it will override the <copy-files> setting:
Installation
1) Install package vasek-purchart/phing-copy-files-task with Composer:
2) Register this task under a name of your choosing.
There are several ways how to register a task, see the TaskDefTask documentation. The recommended way is putting this in your build.xml:
You can pick any other name for the command if you would like to.
