project-dependency-strategy

Description

This strategy can be used to check if the classpath entry is in project dependencies.

It will look if one project dependency matches with given organisation and given module name.
If found, it will use the revision specified in the dependency.
If not found it will look if one project dependency matches with given organisation. If found it will use both module name and revision specified in the dependency

Arguments

Parameter name Description Mandatory
pathid name of the path id to fill true
organisation organisation name to search
module module name to search
conf configuration name
Default: default
settingsRef A reference to the ivy settings that must be used by this task
Default: ${project.ivy.instance}

Example

<ea:project-dependency-strategy org="org.codehaus.groovy" module="groovy-all" revision="1.0" />