Ivy resolver hits the server each time

[Joshua Tharp <jo...@alumni.calpoly.edu>]

I'll just start out with a portion of my settings file.

  <resolvers>
    <filesystem
        name="local"
        checkmodified="true"
        changingMatcher="regexp"
        changingPattern=".*_SNAPSHOT">
      <ivy pattern="${ivy.local.default.root}/${repo.ivy.pat}" />
      <artifact pattern="${ivy.local.default.root}/${repo.artifact.pat}" />
    </filesystem>

    <url name="shared">
      <ivy pattern="${repo.root}/${repo.ivy.pat}" />
      <artifact pattern="${repo.root}/${repo.artifact.pat}" />
    </url>

    <packager
        name="public"
        buildRoot="${ivy.default.ivy.user.dir}/packager/build"
        resourceCache="${ivy.default.ivy.user.dir}/packager/cache">
      <ivy pattern="${repo.root}/${repo.ivy.pat}" />
      <artifact pattern="${repo.root}/${repo.packager.pat}" />
    </packager>
  </resolvers>

I'm using a copy of the Ivyroundup repository on my server and only resolve
certain packages locally (that's why I have two resolvers pointed to the
same repository). In my Ant script I call resolve on each build and my build
is going out to the server each build. For revision specs that aren't exact
1.1.+ for example, I can see why Ivy would need to be the case, but I have a
number of specific versions specified in my ivy files and it still seems
that Ivy is going out to my server with each build. Shouldn't it be using
the cache? What am I doing wrong?

Thanks,

Josh