[ https://issues.apache.org/jira/browse/SLING-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls updated SLING-8421: ------------------------------ Fix Version/s: slingfeature-maven-plugin 1.0.4 > Allow artifact providers that work with URLs instead of Files > ------------------------------------------------------------- > > Key: SLING-8421 > URL: https://issues.apache.org/jira/browse/SLING-8421 > Project: Sling > Issue Type: Improvement > Components: Feature Model > Affects Versions: Feature Model 1.0.2, Feature Model IO 1.0.2, Feature > Model Analyser 1.0.2, Feature Model Launcher 1.0.2, Feature Model Converter > 1.0.2, slingfeature-maven-plugin 1.0.2, Feature Model API Regions Extension > 1.0.2, Feature Model Content Extension 1.0.2 > Reporter: Karl Pauls > Assignee: Karl Pauls > Priority: Major > Fix For: Feature Model 1.0.4, Feature Model IO 1.0.4, Feature > Model Analyser 1.0.4, Feature Model Launcher 1.0.4, Feature Model Converter > 1.0.4, Feature Model API Regions Extension 1.0.4, Feature Model Content > Extension 1.0.4, slingfeature-maven-plugin 1.0.4 > > Time Spent: 2h > Remaining Estimate: 0h > > The way we set-up the feature io (and subsequently, the way the launcher > currently uses it) there is a build-in assumption that artifacts are > available as local files. While that makes some sense there are scenarios > where it would be more efficient to not require them to be Files unless it is > really needed. We should make it possible for a provider to hand out URLs > instead of Files and prefer to use those URLs where possible as a File can be > easily accessed via a URL but the reverse is not true without locally > buffering the URL content as a File. -- This message was sent by Atlassian JIRA (v7.6.3#76005)