<!DOCTYPE html>

<html>
    
    
    
    <head>
        <meta http-equiv="content-type" content="text/html; charset=utf-8">
        <meta name="viewport" content="width=device-width, initial-scale=1">
        <meta name="robots" content="noindex">
        <meta name="description" content="The ivysettings.xml file holds a chain of Ivy resolvers for both regular artifacts and Ivy module files. These are used to resolve and publish (i.e. deploy) artifacts.

There are a two ways to configure resolvers in ivysettings.xml to set up Ivy to work with Artifactory:

Automatically, using the Artifactory Ivy Settings Generator
Manually defining IBiblio and URL resolvers.

Automatic Settings with Artifactory&#39;s Ivy Settings Generator

To begin quickly, you can define credentials and resolver settings using Artifactory&#39;s Ivy Settings Generator. This generates a URL resolver suitable for resolution.

In the Artifact Repository Browser of the Artifacts module, select Set Me Up. In the Set Me Up dialog, set Ivy in the Tool field and click &quot;Generate Ivy Settings&quot;. You can now specify the repositories you want to configure for Ivy.

Since the Libs Repository field only includes virtual or remote repositories, none of these will be suitable for deployment, and you need to modify the deployment URL to point to a local repository.

Select an Ivy Repository Layout

Be sure to select layout that is compatible with Ivy such as ivy-default or a custom layout that you have defined.

Provision Dynamic Settings for Users

Deploy and provision a dynamic settings template for your users.

After being downloaded, settings are generated according to your own logic, and can automatically include user authentication information.

For details, see Provision Build Tool Settings under Filtered Resources.

Define a Manual Resolver

This section reviews the various resolvers that can be defined and include:

The Ibiblio Resolver
The URL Resolver
The Chain Resolver

The IBiblio Resolver and Ivy

This resolver is only used to resolve dependencies. By default, it assumes artifacts in your repository are laid-out in the popular and standard Maven 2 format (which may not always be the case).

The IBiblio resolver can resolve artifacts from remote Maven 2 HTTP repositories, and if you use version ranges it relies on maven-metadata.xml files in the remote repository to gather information on the available versions.

To use the IBiblio resolver, add the following to your ivysettings.xml file:

Note

The URL specified in the root property must point to an Artifactory repository. In the above example, it is the pre-configured libs-releases virtual repository.

Them2compatibleproperty configures the resolver with an artifact pattern that follows the standard Maven 2 layout.

The URL Resolver and Ivy

The URL resolver can be used to resolve dependencies and/or for deployment of both regular artifacts and Ivy module files.

To publish or resolve artifacts to or from Artifactory, you need to configure a URL resolver with the pattern that matches your target repository layout for both Ivy and artifact files.

For example:

{/ Authentication required for publishing (deployment). &#39;Artifactory Realm&#39; is the realm used by Artifactory so don&#39;t change it. /}

{/ You can use  m2compatible=&quot;true&quot; instead of specifying your own pattern /}

Note

The URL resolver uses HTML href analysis to learn about the available versions of a remote artifact. This is less reliable than using an IBiblio resolver, however it works well with remote Artifactory servers.

The Chain Resolver and Ivy

You can combine resolver definitions under a chain resolver in Ivy which uses a set of sub resolvers to resolve dependencies and for publishing.

For details please refer to the Ivy documentation for Chain Resolver.">
        <title>Integrations -&gt; Working with Ivy -&gt; Ivy Settings - ivysettings.xml</title>
        <link rel="canonical" href="https://jfrog.com/help/v/u/integrations-working-with-ivy-ivy-settings-ivysettings.xml">
        <link rel="stylesheet" href="https://jfrog.com/help/stylesheets/ssr-default-styles.css">
    </head>
    <body>
        <header>
            <h1>Integrations -&gt; Working with Ivy -&gt; Ivy Settings - ivysettings.xml</h1>
            <a href="https://jfrog.com/help/api/khub/documents/UqiWePoVLpnAAeUIP6TdTw/content">
                <h2>external_document</h2>
            </a>
            <dl>
                
                    <dt>Products</dt>
                    <dd>JFrog Platform</dd>
                
                    <dt>Content Type</dt>
                    <dd>Integrations</dd>
                
            </dl>
        </header>
        <footer>
            <a id="backToHome" href="https://jfrog.com/help/">Back to home page</a>
        </footer>
    </body>
</html>
