[
https://issues.apache.org/jira/browse/SLING-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847380#comment-16847380
]
Robert Munteanu commented on SLING-8391:
----------------------------------------
Another nit - when I run a command without a valid repository id it fails with
a NPE:
{noformat}$ ./run.sh release update-reporter
Failed running command
java.lang.NullPointerException: null
at
org.apache.sling.cli.impl.release.UpdateReporterCommand.execute(UpdateReporterCommand.java:64)
at
org.apache.sling.cli.impl.CommandProcessor.runCommand(CommandProcessor.java:69)
at
org.apache.sling.cli.impl.ExecutionTrigger.lambda$activate$0(ExecutionTrigger.java:33)
at java.base/java.lang.Thread.run(Unknown Source)
{noformat}
I think we should be more user-friendly here.
> Add support for execution modes
> -------------------------------
>
> Key: SLING-8391
> URL: https://issues.apache.org/jira/browse/SLING-8391
> Project: Sling
> Issue Type: New Feature
> Components: Tooling
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The Commiter CLI tool should provide support for the following execution
> modes:
> # dry-run - default mode, which only lists the output of a command
> # interactive - lists command output, but based on user-input can also
> execute actions on behalf of the user (e.g. send email, release artifacts,
> update site, etc.)
> # auto - runs the command, assuming the default actions / answers
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
