Modify ↓
Ticket #108 (closed defect: fixed)
inconsistant naming of task
| Reported by: | anonymous | Owned by: | hans |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | phing-core | Version: | 2.2.0 |
| Keywords: | documentation | Cc: |
Description
From Appendix B: Core Tasks
CallTargetTask
The CallTargetTask calls a target from the same project. A <phingcall> tag may contain <property> tags that define new properties. In the following example, the properties property1 and foo are defined and only accessible inside the called target.
phing/classes/phing/tasks/defaults.properties has:
phingcall=phing.tasks.system.PhingCallTask
Would it be better to rename this task to PhingCallTask, so it matches the naming convention for built-in tasks, rather than calling it CallTargetTask?
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

Fixed in r207, thanks!