Liam Seamus Coughlin
Liam Seamus Coughlin
This would be a hugely useful feature that I would love to see!
Supporting LSP seems like a bigger issue for groovy then just supporting eclipse. Getting decent LSP support in opens the door to vscode and eclipse che and other more "modern"...
+1 Honestly, if Config just had a source() method that would be enough to write our own "config echo" methods off Config.traverse() Something like: ``` var config = configBuilderWithAllMySourcesInIt() .disableEnvironmentVariablesSource()...
Sure - simple does not necessarily mean easy, I just noticed from poking it with a debugger that the value is already there in a lot of the concretes -shrug-
The maven module you're using only adds the last 'exports' specified to the generate module-info.java You should really just update the project to at least jdk17 because we're several LTS...
It's also not in the wrong place -- that's the correct place for it to be in a multi-release jar. https://www.baeldung.com/java-multi-release-jar