# Dual Resolver In some cases, your module descriptions (i.e. Ivy files, maven poms) are located separately from the module artifacts (i.e. jars). So what can you do about it? Use a Dual resolver! And this tutorial will show you how. # project description Let's have a look at the `src/example/dual` directory in your Ivy distribution. It contains a build file and 3 directories: settings: contains the ivy settings file repository: a sample repository of ivy files project: the project making use of Ivy with dual resolver ## the dual project The project is very simple and contains only one simple class: `example.Hello` It depends on two libraries: Apache commons-lang and Apache commons-httpclient. Here is the content of the project: build.xml: the ant build file for the project ivy.xml: the ivy project file src\example\Hello.java: the only class of the project Let's have a look at the `ivy.xml` file:
    <ivy-module version="1.0">
        <info organisation="org.apache" module="hello-ivy"/>
        <dependencies>
            <dependency org="commons-httpclient" name="commons-httpclient" rev="2.0.2"/>
            <dependency org="commons-lang" name="commons-lang" rev="2.0"/>
        </dependencies>
    </ivy-module>
As you can see, nothing special here... Indeed, Ivy's philosophy is to keep ivy files independent of the way dependencies are resolved. ## the ivy settings The ivy settings are defined in the `ivysettings.xml` file located in the `settings` directory. Here is what it contains, followed by an explanation.
    <ivysettings>
      <settings defaultResolver="dual-example"/>
      <resolvers>
        <dual name="dual-example">
          <filesystem name="ivys">
            <ivy pattern="${ivy.settings.dir}/../repository/[module]-ivy-[revision].xml" />
          </filesystem>
          <ibiblio name="ibiblio" m2compatible="true" usepoms="false" />
        </dual>
      </resolvers>
    </ivysettings>
Here we configured one resolver, the default one, which is a dual resolver. This dual resolver has two sub resolvers: the first is what is called the "ivy" or "metadata" resolver of the dual resolver, and the second one is what is called the "artifact" resolver. It is important that the dual resolver has exactly two sub resolvers in this given order. The metadata resolver, here a filesystem one, is used only to find module descriptors, in this case Ivy files. The setting shown here tells Ivy that all ivy files are in the `repository` directory, named with the pattern: `[module]-ivy-[revision].xml`. If we check the `repository` directory, we can confirm that it contains a file named `commons-httpclient-ivy-2.0.2.xml`. This file matches the pattern, so it will be found by the resolver. The artifact resolver is simply an ibiblio one, configured in m2compatible mode to use the maven 2 repository, with `usepoms="false"` to make sure it won't use maven 2 metadata. Note that this isn't necessary, since the second resolver in a dual resolver (the artifact resolver) is never asked to find module metadata. # walkthrough ## step 1 : preparation Open a DOS or shell window, and go to the `dual` directory. ## step 2 : clean up On the prompt type : `ant` This will clean up the entire project directory tree (compiled classes and retrieved libs) and the Ivy cache. You can run this each time you want to clean up this example. ## step 3 : run the project Go to the project directory. And simply run `ant`.
    [ivy@apache:/ivy/dual/project]$ ant
    Buildfile: /ivy/dual/project/build.xml

    resolve:
    [ivy:retrieve] :: Ivy 2.2.0 - 20100923230623 :: http://ant.apache.org/ivy/ ::
    [ivy:retrieve] :: loading settings :: file = /ivy/dual/settings/ivysettings.xml
    [ivy:retrieve] :: resolving dependencies :: org.apache#hello-ivy;working@apache
    [ivy:retrieve] 	confs: [default]
    [ivy:retrieve] 	found commons-httpclient#commons-httpclient;2.0.2 in ivys
    [ivy:retrieve] 	found commons-logging#commons-logging;1.0.4 in ibiblio
    [ivy:retrieve] 	found commons-lang#commons-lang;2.0 in ibiblio
    [ivy:retrieve] downloading http://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/2.0.2/commons-httpclient-2.0.2.jar ...
    [ivy:retrieve] .................................................................................................................................................................................................................................................................................................................................................................................................................................................... (220kB)
    [ivy:retrieve] .. (0kB)
    [ivy:retrieve] 	[SUCCESSFUL ] commons-httpclient#commons-httpclient;2.0.2!commons-httpclient.jar (3853ms)
    [ivy:retrieve] downloading http://repo1.maven.org/maven2/commons-lang/commons-lang/2.0/commons-lang-2.0.jar ...
    [ivy:retrieve] ................................................................................................................................................................................................................................................................................................................................................ (165kB)
    [ivy:retrieve] .. (0kB)
    [ivy:retrieve] 	[SUCCESSFUL ] commons-lang#commons-lang;2.0!commons-lang.jar (1826ms)
    [ivy:retrieve] downloading http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar ...
    [ivy:retrieve] .......................................................................... (37kB)
    [ivy:retrieve] .. (0kB)
    [ivy:retrieve] 	[SUCCESSFUL ] commons-logging#commons-logging;1.0.4!commons-logging.jar (1341ms)
    [ivy:retrieve] :: resolution report :: resolve 1076ms :: artifacts dl 7036ms
    	---------------------------------------------------------------------
    	|                  |            modules            ||   artifacts   |
    	|       conf       | number| search|dwnlded|evicted|| number|dwnlded|
    	---------------------------------------------------------------------
    	|      default     |   3   |   3   |   1   |   0   ||   3   |   3   |
    	---------------------------------------------------------------------
    [ivy:retrieve] :: retrieving :: org.apache#hello-ivy
    [ivy:retrieve] 	confs: [default]
    [ivy:retrieve] 	3 artifacts copied, 0 already retrieved (423kB/47ms)

    run:
        [mkdir] Created dir: /ivy/dual/project/build
        [javac] /ivy/dual/project/build.xml:58: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
        [javac] Compiling 1 source file to /ivy/dual/project/build
         [java] standard message : hello ivy !
         [java] capitalized by org.apache.commons.lang.WordUtils : Hello Ivy !
         [java] head status code with httpclient: 200
         [java] now check if httpclient dependency on commons-logging has been realized
         [java] found logging class in classpath: interface org.apache.commons.logging.Log

    BUILD SUCCESSFUL
    Total time: 10 seconds
As you can see, Ivy not only downloaded commons-lang and commons-httpclient, but also commons-logging. Indeed, commons-logging is a dependency of httpclient, as we can see in the httpclient ivy file found in the `repository` directory:
    <ivy-module version="1.0">
        <info
            organisation="commons-httpclient"
            module="commons-httpclient"
            revision="2.0.2"
            status="release"
            publication="20041010174300"/>
        <dependencies>
            <dependency org="commons-logging" name="commons-logging" rev="1.0.4" conf="default"/>
        </dependencies>
    </ivy-module>
So everything seemed to work. The ivy file was found in the `repository` directory and the artifacts have been downloaded from ibiblio. This kind of setup can be useful if you don't want to rely on the maven 2 repository for metadata, or if you want to take full advantage of Ivy files for some or all modules. Combining chain and dual resolvers should give you enough flexibility to meet almost any requirement. For full details about the dual resolver, have a look at the corresponding reference documentation.