-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure or disable behavior wrt. command-line arguments? #508
Comments
The same in my project too. With spring boot configuration additional location argument: |
This is a side effect that we now support commands without entering interactive shell. You could use any other boot style to define it's options like ENV variables. I'm just thinking what should we do about this if we'd somehow allow user to pass properties to a shell app? It's a common way to pass properties to boot app via command-line arguments but how to differentiate arguments for boot app itself vs. shell app. |
Ran into this today. For me, same exception as above when passing |
Pls. fix this. |
In my project, I use https://github.com/fonimus/ssh-shell-spring-boot . This has recently been upgraded to use version 2.1.0 of Spring Shell.
My application makes use of command-line arguments. Now, I observe that Spring Shell tries to interpret the command-line argument as a shell command and execute it. This results in an error on application start since no matching command is registered, obviously:
I checked the documentation but could not find an answer to my question: (How) can I adapt this command-line argument parsing or maybe completely disable it?
The text was updated successfully, but these errors were encountered: