Merge multiple OpenAPI definitions

[cbarlin]

Resolves #51

I've marked this as draft in case you want to change the approach taken, and because I've yet to fully finish the testing. The remaining changes are:

• Add another tests module that builds off of test-javalin-jsonb so we can check it correctly pulls in from libraries
• Adjust the github pipelines to ensure that the plugin is being used

I'm also not sure if this should be a separate goal or just part of the existing one.

I was also thinking possibly (as a second PR) of moving the json serialisation of the OpenAPI spec to a library, and the http-generator-core can use that to serialise/deserialise

Another thing I thought of as I was working on this is that this change works for libraries that have OpenAPI definitions, but not for ones in which there's no javadoc available for the annotation processor to parse... Is it worth adding the ability to parse Schema annotations as well?

[cbarlin]

Running this through a semantic diff tool, there is a bunch of added exampleSetFlag items, and the description items from the moar-openapi.json file above.

[cbarlin]

So with the layout of the tests right now, the only way to test the plugin is to either release or install the plugin, and then run the tests with that version. The latter means that we can get rid of the separate test for the plugin and change the instructions for the main tests to cd ./openapi-maven-plugin && mvn install && cd .. && <existing instructions> but then means that the committed tests has to reference an installed snapshot and/or reference a version that hasn't been released, neither of which are great. If it's released without testing, that's not great either.

We could restructure the plugin so it's part of the same versioning and parent pom as the other items in the repository, like the avaje-inject plugin is - that would probably cause the least amount of change?

Any thoughts? I'm going on holidays at the end of this week so won't be able to do anything after that.

[cbarlin]

@rbygrave I'm still on holidays but will be back soon. What are your thoughts on making the plugin versioned alongside the rest of the project?

We can then also spin the jsonb stuff for the OpenAPI schema into a seperate module and then the http-generator-core can use it too.

[rbygrave]

This PR is still DRAFT per se ... but yeah I'm pretty happy with it.

What are your thoughts on making the plugin versioned alongside the rest of the project?

Maybe sort out this PR first?

We can then also spin the jsonb stuff for the OpenAPI schema into a seperate module and then the http-generator-core can use it too.

Yes, could be a good followup.

[cbarlin]

The thing blocking this PR is (mostly) the lack of testing, and that requires the plugin be versioned alongside the rest of the project. But I'll take that as approval to do that in order to get the tests going 😁