You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/10/01 12:43:00 UTC
[jira] [Resolved] (SLING-7965) Scanner should not require
ArtifactManager
[ https://issues.apache.org/jira/browse/SLING-7965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-7965.
-------------------------------------
Resolution: Fixed
Assignee: Carsten Ziegeler
Created a temporary ArtifactProvider SPI in the analyser module in rev dbb9187
> Scanner should not require ArtifactManager
> ------------------------------------------
>
> Key: SLING-7965
> URL: https://issues.apache.org/jira/browse/SLING-7965
> Project: Sling
> Issue Type: Task
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model Analyser 0.1.4
>
>
> The scanner currently requires the artifact manager which is capable of resolving any url to get an artifact. However, when embedding the scanner/analyser into tools like Maven this is too much flexibility and all that is needed is an interface which can resolve an artifact id to a file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)