Max Rydahl Andersen

@fbricon is this not more due to #2069 where we stopped hard failing in info tools and instead have json be reported even if there are issues? this one is...

> You a tool could say: hey the error is probably something to do with the dependencies because "resolvedDependencies" is missing. But! It could also be that something failed before...

> So a single "error" element would actually be sufficient. what if error happens when collecting the referenced jars or source projects? those would be in addition to the maven...

> No, not in addition to, any issue in resolving dependencies, be it Maven or downloading a Jar or trying to obtain a source project will fail the entire process....

Yeah; unfortunately means it seem to format beyond what it been told afaics. The code is all valid so it has no need to go expand into lines explicitly told...

@quintesse i'm thinking we could probably put this into resourceResolvers - add a call to `PropertiesValueResolver.replaceProperties(item, ...)` in select places. I think we didn't do that in start as a)...

yes and no. `--native` attempts to create a native binary but that only works with dependencies that are "outofthebox" graalvm native-image friendly. Idea from this one is to be able...

I Think we got uberjar, and ability to Build that caches so i think it is covered. Original tweet been deleted so cant check. Closing until convinced otherwise.

seems back to old issue around validation assuming you have a git project... i dont have that yet. just trying things out. thats why im getting this isse. should jreleaser...

actually a git repo and aa commit does not seem to be enough