[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ivy-commits
Subject:    [jira] Commented: (IVY-517) The deprecated "keep" attribute on post
From:       "Maarten Coene (JIRA)" <jira () apache ! org>
Date:       2007-05-31 19:06:15
Message-ID: 3047074.1180638375630.JavaMail.jira () brutus
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/IVY-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500450 \
] 

Maarten Coene commented on IVY-517:
-----------------------------------

Well,

it is in the documentation, but not in the attribute list of the post-resolve task, \
but in the text above it. I had to search a while to find it myself.... But I don't \
see why this attribute should be deprecated? If you do an inline resolve, the result \
of the resolve won't be kept in-memory, even if you use a resolveId. If you set keep \
to true, the result will be kept in-memory.

Or did I miss something here?

> The deprecated "keep" attribute on post resolve tasks causes an error
> ---------------------------------------------------------------------
> 
> Key: IVY-517
> URL: https://issues.apache.org/jira/browse/IVY-517
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0.0-alpha-1
> Environment: Ant 1.7 and Windows XP
> Reporter: Scott Goldstein
> Assignee: Maarten Coene
> Priority: Minor
> Fix For: 2.0.0-alpha-2
> 
> 
> Steps to Reproduce:
> 1.  Create an ant build file to build a product/library which will utilize ivy
> 2.  Create an ant target which uses a post resolve task, such as "ivy:cachepath".  \
> Add to the task the attribute "keep" with any value, such as "true" 3.  Run the \
> build Expected results:
> 1.  The build runs with no errors and adheres to the value of the "keep" attribute \
> as described in Ivy 1.4.1 documentation Actual Results:
> 1.  An error occurs, "build.xml:22: ivy:cachepath doesn't support the "keep" \
> attribute"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]