Correct docs generation

[holly-cummins]

See discussion in #236 (comment)

@gsmet, thank you for your help. Does this look better?
I think I now understand the intention of the changes :)

(... although I still don't understand how my previous version built cleanly.)

[gsmet]

Yes.

quarkus-config-doc-maven-plugin is only used in the docs module. That's where you need the version defined. And that's what it does with this commit given the the version in the pluginManagement of the root pom will be inherited by the docs module.

With the previous version, you were defining the version in modules where you didn't use the plugin.

Now, things can work for several reasons:

• if you enforce the version in the docs module directly when declaring the plugin
• if you're lucky enough that the latest version of the quarkus-config-doc-maven-plugin (that's what Maven will use if no version is defined) is compatible with what the version of the extension annotation processor will produce. So it might work for a few versions and then suddenly get broken. It could also be broken in a subtle way that doesn't fail the build.

The version of quarkus-config-doc-maven-plugin should be the same as the version of the extension annotation processor.

[holly-cummins]

Ahh, thanks @gsmet. It was probably picking up the latest, and that's why it seemed to work.