- Documentation (trunk)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
|Handle latest||yes with http urls (and apache server) and with file urls, no with other urls|
|Handle publish||yes with http urls whose destination supports publishing (as of Ivy 2.0)|
This resolver is one of the most generic. In fact, most of the previous resolvers can be obtained by a particular configuration of this one. Indeed it uses urls to find ivy files and artifacts. The urls it uses are defined through ivy and artifact children, each giving a pattern to find ivy files or artifacts.
Limitation: in m2compatible mode, this resolver is not able list available organizations. It means some features like repreport are not available.
AttributesThis resolver shares the common attributes of standard resolvers.
|m2compatible||True if this resolver should be maven2 compatible, false otherwise since 1.3||No, defaults to false|
|ivy||defines a pattern for ivy files, using the pattern attribute||0..n|
|artifact||defines a pattern for artifacts, using the pattern attribute||1..n|
<url name="two-patterns-example">Looks for ivy files in one place and for artifacts in two places: with or without revision in name (revision being already in the directory structure).
<ivy pattern="http://ivyrep.mycompany.com/[module]/[revision]/ivy-[revision].xml" />
<artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact]-[revision].[ext]" />
<artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact].[ext]" />