- Documentation (2.3.0-rc2)
- Release Notes
- Tutorials
- Reference
- Introduction
- Settings Files
- Ivy Files
- Ant Tasks
- Using standalone
- OSGi
- Developer doc
IBiblio Resolver
Tag | ibiblio |
Handle latest | yes, at least if the repository server is apache based |
Handle publish | no |
since 1.4 When using the m2compatible flag, you can disable the use of poms by setting the usepoms flag to false. It is then roughly equivalent to a url resolver configured like this:
<url name="test" m2compatible="true">since 2.0 When used in m2compatible mode with the default pattern, this resolver uses maven-metadata.xml files (if present) to list the revisions available on the repository. This is especially useful when using a maven specific proxy, which does not serve directory listing. This can be disabled by using the useMavenMetadata flag.
<artifact pattern="http://repo1.maven.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
</url>
Limitation: in m2compatible mode, this resolver is not able list available organizations. It means some features like repreport are not available.
Attributes
This resolver shares the common attributes of standard resolvers.Attribute | Description | Required |
---|---|---|
root | the root of the artifacts repository. | No, defaults to ${ivy.ibiblio.default.artifact.root} |
pattern | a pattern describing the layout of the artifacts repository. | No, defaults to ${ivy.ibiblio.default.artifact.pattern} |
m2compatible | True if this resolver should be maven2 compatible, false otherwise since 1.3 | No, defaults to false |
usepoms | True if this resolver should use maven poms when it is already in m2compatible mode, false otherwise since 1.4 | No, defaults to true |
useMavenMetadata | True if this resolver should use maven-metadata.xml files to list available revisions, false to use directory listing since 2.0 | No, defaults to true |
Examples
<ibiblio name="maven2" m2compatible="true"/>Defines a resolver called "maven2" using the maven 2 public repository to find module metadata (using maven 2 poms) and artifacts.
<ibiblio name="maven" m2compatible="true" usepoms="false"/>Same as above, but doesn't use poms, only artifacts.