All resolvers of the same type share some common features and attributes detailed here.

Features

validation

All standard resolvers support several options for validation.

The validate attribute is used to configure if ivy files should be checked against the ivy file xml schema.

The checkconsistency attribute allows you to enable or disable consistency checking between what is expected by Ivy when it finds a module descriptor, and what the module descriptor actually contains.

The descriptor attribute lets you define if module descriptors are mandatory or optional.

The checksums attribute is used to define the list of checksums files to use to check if the content of downloaded files has not been corrupted (eg during transfer).

force

Any standard resolver can be used in force mode, which is used mainly to handle local development builds. In force mode, the resolver attempts to find a dependency whatever the requested revision is (internally it replace the requested revision by 'latest.integration'), and if it finds one, it forces this revision to be returned, even when used in a chain with returnFirst=false.

By using such a resolver at the beginning of a chain, you can be sure that Ivy will pick up whatever module is available in this resolver (usually a private local build) instead of the real requested revision. This allows to handle use case like a developer working on modules A and C, where A -> B -> C, and pick up the local build for C without having to publish a local version of B.since 2.0

Attributes

Attribute

Description

Required

Composite

Standard

name

the name which identifies the resolver

Yes

Yes

Yes

validate

indicates if resolved ivy files should be validated against ivy xsd

No, defaults to call setting

Yes

Yes

force

Indicates if this resolver should be used in force mode (see above). since 2.0

No, defaults to false

No

Yes

checkmodified

Indicates if this resolver should check lastmodified date to know if an ivy file is up to date.

No, defaults to ${ivy.resolver.default.check.modified}

No

Yes

changingPattern

Indicates for which revision pattern this resolver should check lastmodified date to know if an artifact file is up to date. since 1.4. See cache and change management for details.

Indicates if this resolver should check the given revision even if it's a special one (like latest.integration). since 1.3

No, defaults to ${ivy.default.always.check.exact.revision}

No

Yes

namespace

The name of the namespace to which this resolver belons since 1.3

No, defaults to 'system'

Yes

Yes

checkconsistency

true to check consistency of module descriptors found by this resolver, false to avoid consistency check since 1.3

No, defaults to true

No

Yes

descriptor

'optional' if a module descriptor (usually an ivy file) is optional for this resolver, 'required' to refuse modules without module descriptor since 2.0

No, defaults to 'optional'

No (except dual)

Yes

allownomd

DEPRECATED. Use descriptor="required | optional" instead. true if the absence of module descriptor (usually an ivy file) is authorised for this resolver, false to refuse modules without module descriptor since 1.4

No, defaults to true

No (except dual)

Yes

checksums

a comma separated list of checksum algorithms to use both for publication and checking since 1.4

Defines a filesystem resolver, named '1', which is then used in two chains, the first which combines the filesystem resolver with an ivyrep resolver, and second which combines the filesystem resolver with an ibiblio resolver, and which returns the first module found, and uses the whole chain to download artifacts (see corresponding resolvers documentation for details about them). Resolver 1 will use a cache named 'cache-1' which should have been defined under the caches element.