Hi Dennis, yes likely, you can also probably starts from the maven plugin which just uses a manually listed set of classes and bypasses cdi integration (since it is at build time without a container launch)
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 15 nov. 2018 à 10:24, Dennis Kieselhorst <[email protected]> a écrit : > Hi, > I want to catch up with this topic and start to think about CXF-7601. My > suggestion is to add a new module description-microprofile-openapi oder > description-openapi-microprofile for it. > > > RMB> Just to update you: we just passed the TCK. Impl is likely not > perfect but I proposed @geronimo to start a 1.0.0 > > RMB> vote with that since we are tck friendly and then iterate with the > classical reports/bugs/... flow. > > RMB> I introduced a very light reflection abstraction to isolate most of > the logic from CDI so assuming the scanning > > RMB> logic is rewritten (this is not much code but it is technology > specific) then it should be quite easy to make it > > RMB> match CXF. Technically, doing a maven plugin to prebuild the > openapi.json is very feasible too (i'm planning to do some tests on this > one soon). > > We would need to implement a replacement for GeronimoOpenAPIExtension, > right? > > Regards > Dennis >
