William Cheng

@JochemKuijpers thanks for the PR. I'll run some tests and try to get it merged before the upcoming v7.6.0 release.

tested locally and the output compiles (except ` jaxrs-cxf-extended`, which has the same issue in the latest master anyway, we will look into it separately)

can you please resolve the merge conflicts when you've time? we will try to get it merged before the v7.6.0 release this weekend

cc @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @martin-mfg (2023/08)

i've just merged https://github.com/OpenAPITools/openapi-generator/pull/18606 to improve the tests in the jaxrs-spec generator. can you please merge the latest master into your branch and add a test or 2 in `modules/openapi-generator/src/test/resources/3_0/jaxrs-spec/petstore-with-fake-endpoints-models-for-testing.yaml`...

update: added a test via https://github.com/OpenAPITools/openapi-generator/pull/18664. please have a look to sese if the result looks good to you.

filed and merged https://github.com/OpenAPITools/openapi-generator/pull/18697 as a follow-up PR

> I wonder if potentially the Api trait that is generated could instead be split up, perhaps for each endpoint. Each trait could contain just a single function. Is this...

Ah ok. I agree with you. To put all operations in a single API file, one can use the openapi normalizer rule `SET_TAGS_FOR_ALL_OPERATIONS`. cc @linxGnu

nice 👍 i'll take another later today