-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using other cxf-xjc-plugins: how to go about that? #1553
Comments
I did have an intermediate solution: by putting it in the normal dependencies under scope |
Thanks for the report, @gkfirst8! I am afraid, there is no good way to do that currently. I'd suggest using the good old cxf-codegen-plugin for now. I guess we could create a new extension inside Quarkus CXF in the same way like we have |
@ppalaga I would like to give it a try. Not to afraid of pom-files ;-) so that should be a good start as I think I read that the other module also just had some pom-magic. Do you have a good start for this? Then I will try to give it a go. (I'm currently travelling so it will have to wait till next week to have me fully start. But I can already read-up on any pointers you can give. (I think the given example already provides nice plugins that could be valuable to the community to be available in quarkus-cxf.)) |
Thanks for being ready to contribute, @gkfirst8 ! Indeed, |
When using CXF-project-external cxf-xjc-plugins we can normally add dependencies to the CXF-plugin in Maven like this:
Where should we add these when using
quarkus-cxf
? We understand thatquarkus-cxf-xjc-plugins
pulls in dependencies in a special way and we tried to put our/these dependencies in these places:quarkus-maven-plugin
pluginBoth result in "XJC reported 'BadCommandLineException' for -xjc argument:-extension -Xnamespace-prefix"
The text was updated successfully, but these errors were encountered: