Uploaded image for project: 'Ivy'
  1. Ivy
  2. IVY-86

Ivy Files are not found in the cache

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.2
    • 1.3-RC1
    • Core
    • None

    Description

      For some reason, even though dependency files themselves can be resovled to the cache, it
      does not seem as if the Ivy configuration files can be loaded from the cache.

      In my ivyconf.xml:

      <resolvers>
      <chain name="remote">
      <filesystem name="internal">
      <ivy pattern="/" />
      <artifact pattern="/" />
      </filesystem>
      <ivyrep name="ibiblio" />
      </chain>

      <filesystem name="local">
      <ivy pattern="/home/jira/.ivy-cache/" />
      <artifact pattern="/home/jira/.ivy-cache/" />
      </filesystem>

      <filesystem name="internal.publish">
      <ivy pattern="/" />
      <artifact pattern="/" />
      </filesystem>

      </resolvers>

      And when a developer builds, we do an
      <ivy:publish resolver="local" />

      Only when we do a full automated build do we want to publish to the internal.publish
      repository (which the same as internal, but i seperate them because the "internal"
      will be exposed by http, and internal.publish will be filesystem.

      However, when I have two modules, A and B, with ivy files:

      A
      -------
      <ivy-module version="1.0">
      <info organisation="test" module="A" revision="1.0" />
      <publications>
      <artifact name="A" type="jar" />
      </publications>
      </ivy-module>

      B
      -------
      <ivy-module version="1.0">
      <info organisation="test" module="B" revision="1.0" />
      <publications>
      <artifact name="B" type="jar" />
      </publications>
      <dependencies>
      <dependency org="test" module="A" rev="1.0">
      <artifact name="A" type="jar" />
      </dependency>
      </dependencies>
      </ivy-module>

      I keep getting a failure to resolve A when i try to build B (after publishing A to cache).
      Basically the reason is that the Ivy.xml is not in the actual repository yet, and for some
      reason it won't try to find it in the cache. In my opinion, it should try to find it in the cache
      if it's there, and I view this is a bug (similar to what maven would do with a pom file)

      Attachments

        Activity

          People

            xavier Xavier Hanin
            mattinger Matthew P. Inger
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: