Janne Valkealahti 041cb30eb0 Fix option type parsing
- In `CommandRegistration` add `ResolvableType` for `OptionSpec` giving
  more spesific handling of a type.
- In `CommandParser` handle source and target types so that we
  have generics with `List`, `Set` and arrays working better.
- In `HandlerMethodArgumentResolver` add better handling for
  `ConversionService` for generic types.
- In `StandardMethodTargetRegistrar` add better types via `ResolvableType`
  now that `CommandRegistration` support it.
- In `OptionConversionCommands` remove converter from `String` to `Set` as
  now things should work as is if generic in a `Set` has a converter.
- Fixes #694
2023-04-02 14:37:08 +01:00
2023-01-23 10:51:57 +00:00
2021-12-17 16:14:37 +00:00
2022-05-31 07:49:50 +01:00
2022-07-18 12:41:23 +03:00
2023-04-02 14:37:08 +01:00
2022-05-06 08:32:53 +01:00
2019-03-26 11:48:55 +01:00
2017-08-08 11:52:31 +02:00
2019-03-26 11:48:12 +01:00
2019-03-26 11:46:51 +01:00
2019-03-26 11:46:51 +01:00
2023-03-24 07:48:26 +00:00
2022-02-22 08:07:05 +00:00

= Spring Shell 2

Spring Shell 2.1.x is a work to solely depend on Spring Boot 2.x and not trying to keep
any backward compatibility with older Spring Shell 1.x nor Spring Boot 1.x.

== Building
```
./mvnw package
```

== Running
The project comes with a sample application, showcasing the various ways you can write commands.

```
./mvnw install
./mvnw -pl spring-shell-samples spring-boot:run
```

From there, try typing `help` or `help <commmand>` at the shell prompt.

Description
No description provided
Readme 9.2 MiB
Languages
Java 100%