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 2019/06/20 20:01:00 UTC

[jira] [Commented] (SLING-8525) Launcher-Extension for CLI invokation of Feature Analyser

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

Carsten Ziegeler commented on SLING-8525:
-----------------------------------------

I don't think a launcher extension is the right way. We should keep things clearly separate. We should have a CLI for the analyser so you can run the analyser separately before the launcher. I think SLING-7929 covers this

> Launcher-Extension for CLI invokation of Feature Analyser
> ---------------------------------------------------------
>
>                 Key: SLING-8525
>                 URL: https://issues.apache.org/jira/browse/SLING-8525
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model
>            Reporter: Dominik Süß
>            Priority: Major
>
> To be able to invoke the Feature Analyser from commandline a dedicated launcher extension should be created which allows to launch features the same way as they would be called for a proper startup but instead calling the currently available AnalyserTasks and exist with a non-zero exit code in case an error was hit while outputting warnings and errors.



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