Add native schema support for org.fugerit.java:fj-doc-base and org.fugeri.tjava:fj-doc-freemarker

[fugerit79]

What does this PR do?

I recently added to one of my project the native metadata needed for GraalVM :
https://github.com/fugerit-org/fj-doc/tree/main/fj-doc-base
https://github.com/fugerit-org/fj-doc/tree/main/fj-doc-freemarker

As for the "CONTRIBUTING" section, the metadata are mantained and tested direcly in my project repository, But as I understand a pull request is needed to be listed here https://www.graalvm.org/native-image/libraries-and-frameworks/

PS: This is my first pull request here, so I hope i filled it property. I tried to read the documentation and I hope I understood it properly.
PSS: Thanks a lot for your great work with GraalVM, we converted already a few production projects to AOT and we are very happy for the gain in

Code sections where the PR accesses files, network, docker or some external service

Tests are note enabled as the metadata and testing is provided direclty on the prohect repository :

https://github.com/fugerit-org/fj-doc

A module test project using https://quarkus.io/ is included :
https://github.com/fugerit-org/fj-doc/tree/main/fj-doc-native-quarkus

And a workflow for continuous testing :
https://github.com/fugerit-org/fj-doc/actions/workflows/build_fj-doc-native-quarkus_test.yml

Checklist before merging

• I have considered including reachability metadata directly in the library or the framework (see our contributing document)
• I am the original author of all content provided in the pull request, and I did not copy the content from any other source (see the tests section from our contributing document)
• For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)
• [ X I have properly formatted metadata files (see our formatting guide)
• [ X I have added thorough tests (see the tests section from our contributing document)
• I have filled all places where my pull request accesses files, network, docker, or any other external service (see the section above)

[fugerit79]

Hello, may I know if got something wrong about the pull request @fniephaus ?

As far as I have understood as we included in the project repository the native metadata, tests and so on are handled on our repository. Is it correct?

Thanks in advance.

[fniephaus]

Apologies for the delay, and thanks for the contribution!

As far as I have understood as we included in the project repository the native metadata, tests and so on are handled on our repository. Is it correct?

Yes, that's correct. There's one minor detail I liked to make you aware of. From the docs

To avoid a situation when constituent parts of a project are built with overlapping configurations, we recommended you use subdirectories within META-INF/native-image: a JAR file built from multiple maven projects cannot suffer from overlapping native-image configurations. For example:

• foo.jar has its configurations in META-INF/native-image/foo_groupID/foo_artifactID
• bar.jar has its configurations in META-INF/native-image/bar_groupID/bar_artifactID

So maybe move your config files into sub directories to avoid any user-side warnings.

[fniephaus]

The new entries will appear on the website very soon.

[fugerit79]

Apologies for the delay, and thanks for the contribution!

As far as I have understood as we included in the project repository the native metadata, tests and so on are handled on our repository. Is it correct?

Yes, that's correct. There's one minor detail I liked to make you aware of. From the docs

To avoid a situation when constituent parts of a project are built with overlapping configurations, we recommended you use subdirectories within META-INF/native-image: a JAR file built from multiple maven projects cannot suffer from overlapping native-image configurations. For example:

• foo.jar has its configurations in META-INF/native-image/foo_groupID/foo_artifactID
• bar.jar has its configurations in META-INF/native-image/bar_groupID/bar_artifactID

So maybe move your config files into sub directories to avoid any user-side warnings.

No problem for the delay, thanks for merging the pull request.
Currently I do not provide an all modules jar.
But this situation applies to maven-shade-plugin or quarkus uber jar?

In case we will change the structure in the next release.

Do we need to change the metadata location too?

        "metadata_locations": [
          "https://github.com/fugerit-org/fj-doc/tree/main/fj-doc-base/src/main/resources/META-INF/native-image"
        ],

[fniephaus]

Currently I do not provide an all modules jar.

The recommendation is not just for modules. group and artifact ID are the Maven coordinates.

In case we will change the structure in the next release.

Great, thank you!

Do we need to change the metadata location too?

I don't think so, the metadata will be in a subdirectory of the linked location, right?

[fugerit79]

Do we need to change the metadata location too?

I don't think so, the metadata will be in a subdirectory of the linked location, right?

Correct, thanks