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)

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

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

Can assign it to me @ia3andy ?

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

#39968