bootique
bootique copied to clipboard
Bootique is a minimally opinionated platform for modern runnable Java apps.
Would be beneficial to have a special value object for credentials (passwords, etc.). This will explicitly mark such properties as confidential and e.g. prevent us from logging their values.
Sometimes it is not enough to run a unit test "app" in a separate thread via BQDaemonTestRuntime. Instead a full subprocess is required. E.g. we can't test https://github.com/nhl/bootique-logback/issues/10 properly (see...
Let's allow `-H` to take an optional argument that will be treated as a config path, so the command would limit printed config to just the children of that path
## Changes - Adds functionality to allow `Command`s to take CLI arguments #### Notes - This does not yet close 347. It only adds functionality for commands to take arguments
The current approach to inflating a factory with configuration is rather verbose: ```java @Singleton @Provides MyType provide(ConfigurationFactory cf, MyOtherType ot) { return cf.config(MyTypeFactory.class, "prefix").create(ot); } // or, after #345 @Singleton...
Let's provide a new core module with a command to self-install a Bootique app as a "service" in the target OS. Initial scope will be limited to `systemd` OS's. ##...
Since Bootique 3.0 introduces support for Jakarta APIs in various modules we may think about adding support for `jakarta.inject` to the Bootique DI