Filename Mapper maps source file name(s) to target file name(s).
Built-in mappers can be accessed by specifying they "type" attribute:
Custom mappers can be specified by providing a dot-path to a include_path-relative
class:
author |
Hans Lellelid hans@xmpl.org |
---|---|
package |
phing.types |
setClasspath(\Path $classpath)
createClasspath()
setClasspathRef(\Reference $r)
setType($type)
setClassname($classname)
setFrom($from)
setTo($to)
setRefid(\Reference $r) : void
Subclasses may need to check whether any other attributes have been set as well or child elements have been created and thus override this method. if they do they must call parent::setRefid()
getImplementation()
getRef()
setDescription($desc)
getDescription()
isReference()
dieOnCircularReference($stk, \Project $p)
If one is included, throw a BuildException created by circularReference
This implementation is appropriate only for a DataType that cannot hold other DataTypes as children.
The general contract of this method is that it shouldn't do anything if checked is true and set it to true on exit.
getCheckedRef($requiredClass, $dataTypeName)
tooManyAttributes()
noChildrenAllowed()
circularReference()
parsingComplete() : void
setProject(\Project $project)
getProject() : \Project
log(string $msg, integer $level = \Project::MSG_INFO)
string
The message to be logged.
integer
The message's priority at this message should have
type :
classname :
from :
to :
classpath :
classpathId :
description :
ref :
checked : boolean
Subclasses are responsible for setting this value to false if we'd need to investigate this condition (usually because a child element has been added that is a subclass of DataType).
var |
---|
boolean
project : \Project