Dynamic revisions question

I'm having some difficulty getting dynamic revisions working in
v2.0.0-beta2.  Everything works fine as long as I specify a complete
revision number, for example: <dependency org="commons-logging"
name="commons-logging" rev="1.0.4" transitive="false"/>.  However, if I
attempt to specify a dynamic revision, it won't work.  

For example, this:
  <dependency org="commons-logging" name="commons-logging" rev="1.0.+"
transitive="false"/>

Results in this message:
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: WARNINGS
[ivy:retrieve]          module not found:
commons-logging#commons-logging;1.0.+
[ivy:retrieve]  ==== artifactory: tried
[ivy:retrieve]    -- artifact
commons-logging#commons-logging;1.0.+!commons-logging.jar:
[ivy:retrieve]
http://reposvr:8081/artifactory/repo/commons-logging/commons-logging/1.0
.+/commons-logging-1.0.+.jar
[ivy:retrieve]
http://reposvr:8081/artifactory/repo/commons-logging/commons-logging/[re
vision]/commons-logging-[revision].jar
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]          ::          UNRESOLVED DEPENDENCIES         ::
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve]          :: commons-logging#commons-logging;1.0.+: not
found
[ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::

My ivysettings.xml looks like this (we specify an enterprise repository
running on Artifactory and ibiblio as a fallback).

<ivysettings>
  <settings defaultResolver="chained"/>
    <resolvers>
      <chain name="chained">
        <url name="artifactory">
          <artifact
       
pattern="http://reposvr:8081/artifactory/repo/[organisation]/[module]/[r
evision]/[artifact]-[revision].[ext]" />
        </url>
        <ibiblio name="ibiblio" />
      </chain>
  </resolvers>
</ivysettings>

I have tried several work-arounds including using version range syntax,
'latest.integration' and replacing the url resolver with an ibiblio
resolver with its root and pattern attributes set to the specifics for
our enterprise repository, but to no avail.  Again, if I specify a
complete version number, it works fine, so I know that Ivy is set up
correctly.  Any advice on what I'm doing wrong would be greatly
appreciated.  Thanks in advance.

Jim