IBiblio Resolver

Tag

ibiblio

Handle latest

yes, at least if the repository server is apache based

Handle publish

no

This resolver usually uses ibiblio to find artifacts.

(since 1.3) Using the m2compatible attribute, you can benefit from Maven 2 repository compatibility (convert dots in organisation into slashes, search for POMs, use transitive dependencies of POMs). This setting also affects the default place where the resolver looks for its artifacts to point to the Maven 2 repository. So setting this attribute to true is sufficient to use Maven 2 ibiblio repository.

(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">
  <artifact pattern="https://repo1.maven.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
</url>

(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.

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 artifact repository.

No, defaults to ${ivy.ibiblio.default.artifact.root}

pattern

a pattern describing the layout of the artifact repository.

No, defaults to ${ivy.ibiblio.default.artifact.pattern}

m2compatible

True if this resolver should be Maven 2 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.