Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of cbrown@silverpop.com designates
 65.199.213.62 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CA63E6.47AB0528"
Subject: Consistency check failing on branch information
Date: Thu, 12 Nov 2009 17:20:01 -0500
Message-ID: 
 <6B4D8A42E536AC4EAC179B77DC162AB2015983D0@atl-mail03.corp.int-silverpop.com>
Thread-Topic: Consistency check failing on branch information
Thread-Index: Acpj5kamKEWxAspuTPqZidDxO2oMgA==
From: "Carlton Brown" <cbrown@silverpop.com>
To: <ivy-user@ant.apache.org>

------_=_NextPart_001_01CA63E6.47AB0528
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Can someone explain exactly the purpose of the consistency check that
Ivy performs?   The documentation says it compares checking between what
is expected and what is actually found.   But what is actually
'expected', and why?

=20

Currently I've got a situation where Ivy is failing with "bad branch
name" every time it encounters a module that has a branch name other
than what the dependency declares.    If I turn off the consistency
check then the error disappears, but then I wonder what I am risking by
doing this.

=20

=20

 I don't understand this behavior.   Is it expected for Ivy not to
tolerate modules of multiple different branches in the same resolver?

=20

Thanks,

Carlton


***CONFIDENTIALITY NOTICE and DISCLAIMER*** 
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.
------_=_NextPart_001_01CA63E6.47AB0528--