sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-7965) Scanner should not require ArtifactManager
Date Mon, 01 Oct 2018 12:22:00 GMT

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

Carsten Ziegeler updated SLING-7965:
------------------------------------
    Description: 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.  (was: The analyzer currently requires the artifact manager which is capable
of resolving any url to get an artifact. However, when embedding the analyzer 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.)

> 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
>            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)

Mime
View raw message