Using AdditionalStaticResourceBuildItem is not always working propertly in dev-mode

[ia3andy]

Describe the bug

Currently, if there is no meta-inf/resources files, then Quarkus is using a cache when instantiating the StaticHandler, when using AdditionalStaticResourceBuildItem, we don't necessarily have a meta-inf/resources at buildtime as it's generated.

This leads to caching issue as described here: https://github.com/quarkiverse/quarkus-web-bundler/issues/171

Expected behavior

Files added with AdditionalStaticResourceBuildItem shouldn't be cached in dev-mode.

---

The solution might be to split in to handers:

• one for external resources (from jars like mvnpm or webjars)
• one for local static resources (meta-inf/resources and AdditionalStaticResourceBuildItem) on which cache is disabled in dev mode

[ia3andy]

We discussed it with @cescoffier and here is the proposed solution:

Create a new GeneratedStaticResourceBuildItem(String publicPath, byte[] content), the BuildStep will take care of:

• Creating the GeneratedResourceBuildItem and NativeImageResourceBuildItem
• Creating the route handler:
  • dev: implement a new classpath static handler without cache (or FS if we see there are problems) with support for http compression, head and options requests...
  • prod: instantiate a vert.x static handler (they are in the generated resources so it's fine)

[ia3andy]

Here is what we are trying to avoid: https://github.com/quarkiverse/quarkus-web-bundler/blob/main/deployment/src/main/java/io/quarkiverse/web/bundler/deployment/web/GeneratedWebResourcesProcessor.java

[ia3andy]

For the dev handled, a lot of logic can be extracted from here: https://github.com/vert-x3/vertx-web/blob/master/vertx-web/src/main/java/io/vertx/ext/web/handler/impl/StaticHandlerImpl.java

[mcruzdev]

Can assign it to me @ia3andy ?

[ia3andy]

@mcruzdev I found a good follow issue for you :)

https://github.com/quarkusio/quarkus/issues/39968