Replies: 2 comments
|
I couldn't agree more! I came to the same conclusion when I was reviewing dependencies.. Same thing for reactor dependency , I see no added value of using it in the context of interactive shell applications (even in non interactive mode BTW, with all the complexity in Anyway, I will turn this into an issue and see if we can improve things and drop unnecessary dependencies. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to ask about the rationale for using
spring-messaginginspring-shell. The only reason I can see is to reuseMessageandHandlerMethodArgumentResolveras some kind of generic holder (?) for multiple purposes.Is that really the best approach? It feels a bit bizarre.
Maybe a
spring-shellspecificHandlerMethodArgumentResolvershould be introduced, and the dependency onspring-messagingcould be dropped?All reactions