public class ImportTask extends Task
It must be 'top level'. On execution it will read another Ant file into the same Project.
Important: Trying to understand how relative file references resolved in deep/complex build hierarchies - such as what happens when an imported file imports another file can be difficult. Use absolute references for enhanced build file stability, especially in the imported files.
Examples:
<import file="../common-targets.xml"/>
Import targets from a file in a parent directory.
<import file="${deploy-platform}.xml"/>
Import the project defined by the property deploy-platform
.
description, location, project
Constructor and Description |
---|
ImportTask() |
Modifier and Type | Method and Description |
---|---|
void |
add(ResourceCollection r)
The resource to import.
|
void |
execute()
Called by the project to let the task do its work.
|
protected boolean |
isInIncludeMode()
Whether the task is in include (as opposed to import) mode.
|
void |
setAs(java.lang.String prefix)
The prefix to use when prefixing the imported target names.
|
void |
setFile(java.lang.String file)
the name of the file to import.
|
void |
setOptional(boolean optional)
sets the optional attribute
|
void |
setPrefixSeparator(java.lang.String s)
The separator to use between prefix and target name, default is
".".
|
bindToOwner, getOwningTarget, getRuntimeConfigurableWrapper, getTaskName, getTaskType, getWrapper, handleErrorFlush, handleErrorOutput, handleFlush, handleInput, handleOutput, init, isInvalid, log, log, log, log, maybeConfigure, perform, reconfigure, setOwningTarget, setRuntimeConfigurableWrapper, setTaskName, setTaskType
clone, getDescription, getLocation, getProject, setDescription, setLocation, setProject
public void setOptional(boolean optional)
optional
- if true ignore files that are not present,
default is falsepublic void setFile(java.lang.String file)
file
- the name of the filepublic void setAs(java.lang.String prefix)
public void setPrefixSeparator(java.lang.String s)
public void add(ResourceCollection r)
public void execute()
Task
protected final boolean isInIncludeMode()
In include mode included targets are only known by their prefixed names and their depends lists get rewritten so that all dependencies get the prefix as well.
In import mode imported targets are known by an adorned as well as a prefixed name and the unadorned target may be overwritten in the importing build file. The depends list of the imported targets is not modified at all.