ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brown, Carlton" <>
Subject RE: Use cases of resolver force mode
Date Thu, 08 Jan 2009 14:11:08 GMT
Submitted this as (better
late than never) 

-----Original Message-----
From: Shawn Castrianni [] 
Sent: Thursday, October 23, 2008 12:35 PM
To: ''
Subject: RE: Use cases of resolver force mode

I think I ran into this as well and I think that this suggestion would
work nicely.

Shawn Castrianni

-----Original Message-----
From: Brown, Carlton []
Sent: Thursday, October 23, 2008 10:46 AM
Subject: Use cases of resolver force mode

I have a filesystem resolver which should be forced in some chains, but
not in others.   If I understand correctly, the current design as of RC1
would require me to define a duplicate resolver and change the force
attribute in order to accomplish this.

Isn't it correct that force behavior is meaningful only when the
resolver is part of a chain?  If that is true, then doesn't it make more
sense to assign it as an attribute of a resolver reference in a chain,
like this example:

<chain name="rc" returnFirst="false">
        <resolver ref="final-fs"/>
        <resolver ref="rc-fs" force="true"/> </chain>

<chain name="local" returnFirst="false">
        <resolver ref="final-fs"/>
        <resolver ref="rc-fs"/>
        <resolver ref="local-fs" force="true"> </chain>

This gives much more flexibility in defining chain behavior.  Does
anyone else agree, or is there some use case I've overlooked?

This message contains PRIVILEGED and CONFIDENTIAL information that is
intended only for use by the named recipient. If you are not the named
recipient, any disclosure, dissemination, or action based on the
contents of this message is prohibited. In such case please notify us
and destroy and delete all copies of this transmission.  Thank you.

View raw message