Extension writing guide does not mention how to add a resource for inclusion in native image

[emmanuelbernard]

@Sanne mentioned to me that resource files that should be ready by the native image should be enlisted via Shamrock. I looked at the guide and found no reference to resources. Let's complete the doc.

Also I'm interested in an example :)

[emmanuelbernard]

HotDeploymentConfigFileBuildItem seems to be part of it.

so is UndertowBuildStep

@BuildStep
    SubstrateResourceBuildItem registerSubstrateResources(ArchiveRootBuildItem root,
                                                          ApplicationArchivesBuildItem applicationArchivesBuildItem) throws IOException {
        List<String> res = new ArrayList<>();
        Path resources = applicationArchivesBuildItem.getRootArchive().getChildPath("META-INF/resources");
        if (resources != null) {
            Files.walk(resources).forEach(new Consumer<Path>() {
                @Override
                public void accept(Path path) {
                    if (!Files.isDirectory(path)) {
                        res.add(root.getPath().relativize(path).toString());
                    }
                }
            });
        }
        return new SubstrateResourceBuildItem(res);
    }

[Sanne]

I take it the purpose of this issue is "How end users include their own resources" right? ( +1 we definitely need to help users with that)

When it comes to - for example - ORM's import.sql we automate this.

[Sanne]

Relates to #388

[emmanuelbernard]

No the question was how do I as an extension developer add resources.

For end user, do we need more than the automated addition of META-INF/resources that I see in undertow?

[Sanne]

Yeah I believe we need to make a choice.

Either:

• offer some easy way for end users to add their own resources as well
• be nasty and recommend nobody ever adds custom resources?

[emmanuelbernard]

@Sanne OK. Open a different issue so we don't lose it.

[stuartwdouglas]

HotDeploymentConfigFileBuildItem is not related, it is used to indicate that when a file is modified it should cause a hot deployment.

[emmanuelbernard]

Yes but both make sense in a how to deal with resources in extensions section.