Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of charles@dyfis.net designates
 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Date: Fri, 14 Jun 2013 12:47:02 -0500
Message-ID: 
 <CAEHm_sgfkVJe4F4i_c1pmYivky7vUM=YMPpyXdbNANuD_+M0qA@mail.gmail.com>
Subject: Revision mapping (in namespace.xml) => inconsistent module descriptor
From: Charles Duffy <charles@dyfis.net>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=e89a8f8394039667d004df20d514

--e89a8f8394039667d004df20d514
Content-Type: text/plain; charset=UTF-8

Howdy, all --

I'm trying to map a 3rd-party artifact which has been locally referred to
with the revision number "1.0.0" but is upstream "1.0" using a namespace.

I've posted a complete reproducer (ivysettings.xml, build.xml, and output)
here: https://gist.github.com/charles-dyfis-net/5783838


It looks like the reverse mapping isn't working correctly, causing
validation of the imported descriptor to fail. I've seen this happen when
the reverse mapping isn't functional, but I'm pretty sure that isn't the
case here -- and can't find any places in Ivy's test suite where revision
mapping is tested (grepping for fromsystem and tosystem in the test suite's
XML files comes up for no cases where rev is specified).

Am I missing something here?

--e89a8f8394039667d004df20d514--