Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of xavier.hanin@gmail.com
 designates 64.233.184.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=RgvDJLvEqesQTWwSLjH7iAC24FlpRHZZ/hGnLMmg5gbdCTZf6KsG0/Z2Ee6mm/zwoIcLrbSJef4EIt04FRKY0x/4e4DBplMZ5ggRikoFrx4QZata47v/tzx7aN6ZuFWaN3V9SdmsfOAxuafogyX21EeQ40GBar8LURFCu44PZ/o=
Message-ID: <635a05060705211352j49d9fb39ka591a6b8428081ce@mail.gmail.com>
Date: Mon, 21 May 2007 22:52:56 +0200
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: post resolve tasks and "keep" attribute
In-Reply-To: <478031.33962.qm@web82808.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_87294_12485528.1179780776780"
References: <788568.64794.qm@web82809.mail.mud.yahoo.com>
	 <478031.33962.qm@web82808.mail.mud.yahoo.com>

------=_Part_87294_12485528.1179780776780
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 5/21/07, Scott Goldstein <scottnmeg@sbcglobal.net> wrote:
>
> I've solved my problem by changing the order of execution.
>
>   However, I'm still curious about the "keep" property, as I imagine this
> might come up again.  Any info?


In 2.0 version we have introduced a scope which makes the keep attribute
obsolete. See IVY-366 [1] for details.

However, we try to keep Ivy backward compatible, and it seems that we missed
this compatibility break. Could you open an issue in JIRA about this?

Xavier
[1] https://issues.apache.org/jira/browse/IVY-366

  Scott
>
> Scott Goldstein <scottnmeg@sbcglobal.net> wrote:
>   During my build, I'm trying to run the ant "taskdef" task. As part of
> this task, I need to provide a classpath for the task, which I do using the
> "ivy:cachepath" task and an appropriate ivy file. This works, but the
> resolve necessary to achieve this blows away the resolve data from a
> previous execution of resolve, which breaks the build later on.
>
> So, what I need to do it perform a resolve within a particular scope and
> return the resolve data to its previous state.
>
> I looked at the docs on incubator.apache.org and there is some reference
> to the "keep" attribute both post resolve tasks. This appears to be what I
> need. However, when I try using it with 2.0 alpha, I get an error that the
> attribute does not exist.
>
> What's the status of this attribute? If there another way to achieve what
> I need? Is it just a matter of saving and restoring the resolve properties,
> ivy.organisation, ivy.module, ivy.revision, and
> ivy.resolved.configurations?
>
> Thanks.
>
> Scott
>
>


-- 
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/

------=_Part_87294_12485528.1179780776780--