[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-404) Expose underlying Asset source in the individual API's

[Andrew Rubinger (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKWRAP-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Rubinger updated SHRINKWRAP-404:
---------------------------------------

           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 1.1.0-alpha-2
       Resolution: Done


Upstream: https://github.com/shrinkwrap/shrinkwrap/commit/2189a9715e417b9be3516cdde819e2df14d66bef
                
> Expose underlying Asset source in the individual API's
> ------------------------------------------------------
>
>                 Key: SHRINKWRAP-404
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-404
>             Project: ShrinkWrap
>          Issue Type: Feature Request
>            Reporter: Aslak Knutsen
>            Assignee: Ralf Battenfeld
>             Fix For: 1.1.0-alpha-2
>
>
> In some cases it is interesting to get the 'real source' of an Asset beyond the InputStream. Where on disk is the FileAsset read from?
> Both for Tooling integration and e.g. the JRebel Arquillian extension it is needed to know where a source came from to do the linking.
> File FileAsset.getFile
> String ClassLoaderAsset.getResource
> Class<?> ClassAsset.getClass
> etc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira