[
https://issues.apache.org/jira/browse/SLING-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869244#comment-16869244
]
Dominik Süß commented on SLING-8525:
------------------------------------
[~kpauls], [~cziegeler] please synch up and come up with the consenus you reach
- I was following
https://lists.apache.org/thread.html/b0f760bba9af649893962ac66fbbed7f9ab0af9f1c38be45655453be@%3Cdev.sling.apache.org%3E
and there is clearly a different perspective of the two of you on this topic.
The key for the launcher extension was IIUC to avoid yet another artifact that
has to be shipped with duplicates of the binaries already in the launcher and
consolidate/synch up the usage pattern (at the end the extension adds some kind
auf validation mode to the launcher by adding to the classpath).
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
