I've never seen it used with ivy-8.
However, with LTS 10 you get swagger openapi.json generation out-of the box. And also the swagger-ui to explore the APIs is part of the standard distribution. So I'd consider an upgrade to LTS 10.
See https://dev.axonivy.com/news/9.2 where we praise the out-of-the-box OpenAPI integration.
Meanwhile you could also try to do a workaround:
- e.g. deploy our projects to an ivy-10 engine during the build
- get the openapi.json
This could work for simple REST interfaces, as in theory ivy 8 projects can be deployed to an ivy 10 engine. The steps to make the project basically compliant will be done automatically during deployment. However, if you are referring APIs that no longer exist under 10, runtime errors will occur as the compiled classes will remain untouched.