You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2018/06/08 14:11:00 UTC

[jira] [Commented] (SLING-7717) Create an analyser that can generate initial API Controller feature content

    [ https://issues.apache.org/jira/browse/SLING-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506065#comment-16506065 ] 

David Bosschaert commented on SLING-7717:
-----------------------------------------

Implementation in https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-feature-analyser.git;a=commitdiff;h=ef949505dd43ac5207a9b66c4bcd065f6cf6ef20


> Create an analyser that can generate initial API Controller feature content
> ---------------------------------------------------------------------------
>
>                 Key: SLING-7717
>                 URL: https://issues.apache.org/jira/browse/SLING-7717
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>    Affects Versions: Feature Model Analyser 0.1.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>            Priority: Major
>             Fix For: Feature Model Analyser 0.1.4
>
>
> In order to facilitate projects migrating to use the API Controller as described here https://github.com/apache/sling-org-apache-sling-feature/blob/master/apicontroller.md
> a tool is needed to prepopulate a feature with all the packages that it's exporting. This can then be pruned by the developer to be the actual list of packages.
> The Feature Model Analyser provides a nice framework to implement such a tool with.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)