[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-496) Implement CacheUrlAsset

[Andrew Rubinger (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKWRAP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128893#comment-13128893 ] 

Andrew Rubinger commented on SHRINKWRAP-496:
--------------------------------------------

Correct. :)

So ShrinkWrap takes effort to provide really consistent and expected behaviours out of the box, prioritizing those qualities ahead of convenience.  In that regard ShrinkWrap is a bit of a low-level tool by design.  Now, there are occasions where we have to figure out where to draw the line.  While I see your use case here certainly has merit (cutting time and saving resources in redownloading), I'd prefer not to solve it in the ShrinkWrap API.  But I *could* be convinced otherwise; also interested in the opinions of [~aslak] and [~kpiwko] here.

> Implement CacheUrlAsset
> -----------------------
>
>                 Key: SHRINKWRAP-496
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-496
>             Project: ShrinkWrap
>          Issue Type: Feature Request
>          Components: api
>    Affects Versions: 1.2.3
>            Reporter: Alex Soto
>            Priority: Minor
>
> In ShrinkWrap UrlAsset downloaded an asset from a URL, which can be external and then it creates the Archive element with that info. The problem is that sometimes you might want to download a big file (2MB) to put inside an Archive, and this means that for each test class that you execute you end up by downloading this file.
> A possible solution could be create a CacheUrlAsset that downloads the content and stores it in {java.io.tmp}/shrinkwrap so in successive calls before downloading the file again, it can take it directly from cache directory.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)