Modify

Ticket #108 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

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

comment:1 Changed 5 years ago by mrook

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in r207, thanks!

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.