Not compatible with newest Jackson about apiee HOT 15 CLOSED

@computas-mop - release is done, 1.0.9 should be available in maven central soon. Shout if there are issues.

from apiee.

Hi @computas-mop ! Good to talk to you again.
Yes, this is a bit of a mess. I apologize. I never branched properly when work started on Swagger 3 support, and that has not gone anywhere. I think most people moved on to using MicroProfile OpenAPI that usually comes with swagger UI, or if not, you can use Microprofle-ext.

So, back to this, I think the best course of action would be to branch current master to a swagger-3 branch, and if anyone is keen to implement that it can happen there, then we revert the current master to reflect the latest release, then we apply your changes and do a new release.

w.d.y.t ?

Out of interest, what application server are you using this on ? Most of my effort is now in SmallRye OpenAPI where we implement MicroProfile OpenAPI and have much better swagger ui support. Maybe that is something you can migrate too ? (Although there will be a package name change effort)

from apiee.

Likewise, Philip! Hope you're doing well in these challenging times.

I think your proposition sounds good. As the Swagger 3 support is not completed (and tbh probably won't be), it sounds like a good idea to revert master to the 1.0.8 state.

We migrated from Weblogic to Wildfly 18 a year ago, and currently I'm working on upgrading to Wildfly 22. Upgrading to OpenAPI 3 was initially part of the upgrade, but we've chosen to do that as a separate step (as we've ran into some trouble with date serialization/deserialization that we'll have to figure out.)

from apiee.

Ok great. I'll try and do it a.s.a.p. (You are of course also welcome to do it if you are keen)

The good news with Wildfly is that have support for MicroProfile OpenAPI, and you can add MicroProfile-ext OpenApi-ui to get swagger-ui.

from apiee.

I have a branch ready for the OpenAPI v2 version, but it seems I can't create branches in this repo, not even suggest new branches when I create a PR.

My plan: Create a new main branch, based on this commit: 7742faf

Then rename the current master to OpenAPI3.

And then make main the default branch of the repo.

from apiee.

Good idea !!! Let me give you access.... hold on

from apiee.

You should have got a mail to join the project. After you joined I can give you access.

from apiee.

You should have got a mail to join the project. After you joined I can give you access.

Great, thanks. I just accepted.

from apiee.

Ok, can you create branches now ?

from apiee.

Yep, works like a charm. PR coming up.

from apiee.

That's it, I think. Now main is OpenAPI 2, and the OpenAPI3 branch is, well, OpenAPI3 (that is, identical to master. So now I think the next step is to make main the default branch of the repo, and delete the master branch.

And then release a 1.0.9 on Maven central based on main.

from apiee.

Awesome !! Thanks for your help.

from apiee.

Once you are ready I can do the release.

from apiee.

Happy to give at least something back after using the tool for years 😃

I'm ready for the release now (from the main branch).

from apiee.

Ok, I'll do it a bit later, thanks again

from apiee.