Jérôme Van Der Linden

Thanks @Frontrider for the feedback. May I ask if you have a running example of a Java / GraalVM Lambda working with powertools (logging) that you could share or if...

No problem @Frontrider, maybe we can do something for the others. Also note that Powertools works with Kotlin ([example](https://github.com/aws-powertools/powertools-lambda-java/tree/main/examples/powertools-examples-core/kotlin))

@kozub, you are right, this is the verify phase. Maybe we should do that together wit the spotbug check (`verify` instead of `install`). For the rest, let's just try !

looks like it runs with spotbugs... don't know what happened. But it is also not super reliable (error 504): https://github.com/jeremylong/DependencyCheck/issues/5702

Closing (as per the above comments)

@jreijn, feel free. I think that's an easy one. Just update the doc, have a look at the examples too. And everywhere we use a logger. Not sure you have...

Using `config.addUriTranslator(URITranslator.prefix("https://json-schema.org", "resource:"));` fixes the problem but would be great to understand why there is a 403 if using the remote version...

https://developers.google.com/protocol-buffers/docs/overview?hl=fr

Can you try to add [here](https://github.com/aws-samples/aws-lambda-function-url-secured/blob/209bc9d2a73dbb6eefed1dc9cf98a9678ede9873/src/infra/FrontendStack.ts#L140): ```ts childProcess.execSync('npm install -g esbuild', execOptions); ```

I completely missed the notification, will have a look, thanks for the reminder