-
Notifications
You must be signed in to change notification settings - Fork 99
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
-Xfluent-builder is not supported #508
Comments
Could you share a code sample of expected ? I've created test project (that I'll push in next v4) and generated code is like : public Address withStreet(String value) {
setStreet(value);
return this;
}
public Address withNumber(int value) {
setNumber(value);
return this;
} So you can chain code like Address a = new Address().withStreet("MyStreet").withNumber(10); |
Moreover, could you tell me from where the |
Hi @laurentschoelens A sample class would invocation would look like,
where FactSet was an unmarshalled class from a given xml. The |
Thanks but the |
One option I'm thinking of is that the xjc plugin responsible of handling I'm also pretty sure you are using the following library : https://github.com/mklemm/jaxb2-rich-contract-plugin which refers to same configuration as yours. I'll try to contact or propose PR to update documentation according to latest version of jaxb-tools. |
Feel free to reopen issue if you still have problems, providing more details. Thanks |
Because the plugin doesn't support JAXB 2 anymore, the "2" has been removed from the artifactId. It's called: |
I used to use
org.jvnet.jaxb2.maven2:maven-jaxb2-plugin v0.14.0
to create builders in generated classes using-Xfluent-builder
However, when I switch to
org.jvnet.jaxb:jaxb-maven-plugin v2.0.9
the argument-Xfluent-builder
is not supported.I tried using the
-Xfluent-api
as mentioned here https://github.com/highsource/jaxb-tools/wiki/JAXB2-Fluent-API-Pluginbut that generates the
with*
methods and not Builder in the generated class.Are builders not supported anymore?
The text was updated successfully, but these errors were encountered: