Return-Path: 
 <ivy-user-return-7492-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 39797 invoked from network); 14 Dec 2010 00:20:19 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 14 Dec 2010 00:20:19 -0000
Received: (qmail 92711 invoked by uid 500); 14 Dec 2010 00:20:19 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 92693 invoked by uid 500); 14 Dec 2010 00:20:19 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 92677 invoked by uid 99); 14 Dec 2010 00:20:19 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 00:20:19 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=10.0
	tests=NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_MED,SPF_PASS,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of dean.hiller@broadridge.com
 designates 64.18.2.167 as permitted sender)
Received: from [64.18.2.167] (HELO exprod7og107.obsmtp.com) (64.18.2.167)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 00:20:12 +0000
Received: from source ([167.212.2.180]) (using TLSv1) by
 exprod7ob107.postini.com ([64.18.6.12]) with SMTP
	ID DSNKTQa4J/shwqVGqpP94yGlsbMGsGdFdWEo@postini.com;
 Mon, 13 Dec 2010 16:19:51 PST
Received: from JOSQHUBA01.jsq.bsg.ad.adp.com (josqhuba01 [149.83.60.74])
	by mail.broadridge.com (8.13.8/8.13.8) with ESMTP id oBE0Jo8F9183476
	for <ivy-user@ant.apache.org>; Mon, 13 Dec 2010 19:19:50 -0500
Received: from DNVREMSA01.jsq.bsg.ad.adp.com ([206.88.42.250]) by
 JOSQHUBA01.jsq.bsg.ad.adp.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Mon, 13 Dec 2010 19:19:50 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: published module exclusions not working?
Date: Mon, 13 Dec 2010 17:19:48 -0700
Message-ID: 
 <7CA0D5FE7FA83048893E9230C1E9C0280B5CCAEF@DNVREMSA01.jsq.bsg.ad.adp.com>
In-Reply-To: <661038.65833.qm@web30801.mail.mud.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: published module exclusions not working?
Thread-Index: AcubG4pCTUi1rxKkTAGRJfJB1Rt3IgACOaQA
References: 
 <7CA0D5FE7FA83048893E9230C1E9C0280B532F13@DNVREMSA01.jsq.bsg.ad.adp.com>
 <661038.65833.qm@web30801.mail.mud.yahoo.com>
From: "Hiller, Dean  (Contractor)" <dean.hiller@broadridge.com>
To: <ivy-user@ant.apache.org>
X-OriginalArrivalTime: 14 Dec 2010 00:19:50.0639 (UTC)
 FILETIME=[9F7257F0:01CB9B24]

Thanks for the response.  Good to know this is the way it is supposed to
work.  Being new, I wasn't even sure of that. It is working with my new
ivysettings.xml which is...

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<ivy-settings>
  <settings defaultResolver=3D"main" />
  <!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->
  <credentials host=3D"8.8.8.8" realm=3D"Artifactory Realm" =
username=3D"admin"
passwd=3D"password"/>
  <resolvers>
  	<chain name=3D"main">
    	<ibiblio name=3D"broadridge" m2compatible=3D"true"
root=3D"http://8.8.8.8:8081/artifactory/libs-releases" />
	    <url name=3D"artifactory-publish">
	    	<artifact pattern=3D
=09
"http://8.8.8.8:8081/artifactory/libs-releases-local/[organization]/[mod
ule]/[revision]/[artifact]-[revision].[ext]"/>
	        <ivy
pattern=3D"http://8.8.8.8:8081/artifactory/libs-releases-local/[organizat=
i
on]/[module]/[revision]/ivy-[revision].xml" />	    =09
	    </url>  =20
    </chain>
  </resolvers>
</ivy-settings>
=20
Dean

-----Original Message-----
From: Maarten Coene [mailto:maarten_coene@yahoo.com]=20
Sent: Monday, December 13, 2010 4:14 PM
To: ivy-user@ant.apache.org
Subject: Re: published module exclusions not working?

Could you provide a concrete example (with portions of the ivy.xml
files) ?

Maarten



----- Original Message ----
From: "Hiller, Dean (Contractor)" <dean.hiller@broadridge.com>
To: ivy-user@ant.apache.org
Sent: Mon, December 13, 2010 6:31:04 PM
Subject: published module exclusions not working?

I have a module that depends on hbase BUT excludes ant(because that
screws up the build).  I then have X modules depending on hbase BUT  ant
is being downloaded even though I excluded it.



I don't know if it matters, but this is a virtual module so I need in
the virtual module for those exclusions to be inherited by the clients
that use them. =20



Ie. We are almost to a place where our projects simply define a tools
dependency, hbase and that is it instead of 60 dependencies in one ivy
file(ie. We are trying to move all that to a reusable virtual module
location).



Thanks,

Dean






This message and any attachments are intended only for the use of the
addressee=20
and
may contain information that is privileged and confidential. If the
reader of=20
the=20

message is not the intended recipient or an authorized representative of
the
intended recipient, you are hereby notified that any dissemination of
this
communication is strictly prohibited. If you have received this
communication in
error, please notify us immediately by e-mail and delete the message and
any
attachments from your system.



     =20
This message and any attachments are intended only for the use of the add=
ressee and
may contain information that is privileged and confidential. If the reade=
r of the =

message is not the intended recipient or an authorized representative of =
the
intended recipient, you are hereby notified that any dissemination of thi=
s
communication is strictly prohibited. If you have received this communica=
tion in
error, please notify us immediately by e-mail and delete the message and =
any
attachments from your system.
=0D