- Documentation (2.5.0-local-20170911195251)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
yes with HTTP URLs (and Apache server) and with file URLs, no with other URLs
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.
m2compatible mode, this resolver is not able list available organizations. It means some features like repreport are not available.
This resolver shares the common attributes of standard resolvers.
True if this resolver should be Maven 2 compatible, false otherwise since 1.3
No, defaults to false
defines a pattern for Ivy files, using the pattern attribute
defines a pattern for artifacts, using the pattern attribute
<url name="two-patterns-example"> <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]"/> </url>
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).