[ 
https://issues.apache.org/jira/browse/IVY-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Blaine Simpson updated IVY-638:
-------------------------------

    Description: 
WIth both 1.4.1 and 2.0.0-alpha-2, cachefileset task returns an empty file set. 
 If I just swap it out for a cachepath, I get a good path.

I've verified that this is not due to a mistake examining the output fileset, 
by swapping the cachefileset task out for a normal ant fileset definition:  The 
path is echoed correctly from the fileset id.

I wonder if this got broken when id handling was changed.  I see a resolved 
issue which says that setid has been deprecated (in 2006) but it has not been:  
setid attribute is still required for cachefileset.

#################################

A week has passed, and nobody seems to care that a basic, documented feature 
completely doesn't work.

>From the Ivy Features page:

    bugs reported by the community are often fixed in only a few days.

  was:
WIth both 1.4.1 and 2.0.0-alpha-2, cachefileset task returns an empty file set. 
 If I just swap it out for a cachepath, I get a good path.

I've verified that this is not due to a mistake examining the output fileset, 
by swapping the cachefileset task out for a normal ant fileset definition:  The 
path is echoed correctly from the fileset id.

I wonder if this got broken when id handling was changed.  I see a resolved 
issue which says that setid has been deprecated (in 2006) but it has not been:  
setid attribute is still required for cachefileset.


> cachefileset task broken
> ------------------------
>
>                 Key: IVY-638
>                 URL: https://issues.apache.org/jira/browse/IVY-638
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 1.4.1, 2.0.0-alpha-2
>            Reporter: Blaine Simpson
>
> WIth both 1.4.1 and 2.0.0-alpha-2, cachefileset task returns an empty file 
> set.  If I just swap it out for a cachepath, I get a good path.
> I've verified that this is not due to a mistake examining the output fileset, 
> by swapping the cachefileset task out for a normal ant fileset definition:  
> The path is echoed correctly from the fileset id.
> I wonder if this got broken when id handling was changed.  I see a resolved 
> issue which says that setid has been deprecated (in 2006) but it has not 
> been:  setid attribute is still required for cachefileset.
> #################################
> A week has passed, and nobody seems to care that a basic, documented feature 
> completely doesn't work.
> From the Ivy Features page:
>     bugs reported by the community are often fixed in only a few days.

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

Reply via email to