-
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
Incorrect resolution of sources with two executions #362
Comments
Hi @szarza First thanks for using maven-jaxb-plugin I think you're currently using phax's fork : https://github.com/phax/maven-jaxb2-plugin, since groupId missmatches our plugin I'll look at log provided and keep you updated. Regards |
Fast analysis points that your two executions are done with same generateDirectory :
With two executions, you should use seperate generateDirectory Regards |
I also invite you to move to newer jaxb-basics extension <plugin>
<groupId>org.jvnet.jaxb</groupId>
<artifactId>jaxb2-basics</artifactId>
<version>[latest is 2.0.5]</version>
</plugin> |
I'm sorry for the mistake. Also, changing jaxb-basics org.jvnet.jaxb2_commons by org.jvnet.jaxb gives me the error: Thank you. |
Thanks for your reply, and don't worry, my guess is we could have the same issue with current version. Tried to add a example project with 2 executions and no problem for our current version.
Since I don't know quarkus a lot, could you please attach a sample project to reproduce the issue please ? |
Same output using phax fork's with
|
Since it's working with pure mvn way, I guess quarkus does it differently... |
Hi: I was running "quarkus dev" command (to execute and debugging). I have reduced my project leaving only the part of our interest (attached), and I've tested with the following commands:
In these cases, compiles without errors, but sources under target/generated-sources/xjc/calypso/ are not generated. If I run |
HI @szarza Thanks for the sample Explanations below : when setting schemaDirectory from 2nd execution, we got the below stacktrace
in
in Since it's quarkus class that calls the plugin, I'd rather create an issue in quarkus project, since the plugin only execute what it received. As a workaround, maybe try to split the generation part outside from quarkus and then import the generated-code as maven-dependency ? Regards |
Found why quarkus does this, and it seems for me to be a bug : see io.quarkus.maven.DevMojo#getPluginConfig They merge all the configuration that shares the same goal 🤷♂️
|
PR created : quarkusio/quarkus#35846 |
Hi @szarza PR merged in main |
Hi @laurentschoelens: ` ` I don't know how to doit. |
Here is the link of checking if issue is fixed in main in quarkus wiki using snapshots 😄 |
@szarza quarkus 3.4.0 has been released (followed by 3.4.1). |
Hi @laurentschoelens: |
Closing issue as fixed by quarkus |
Environment:
Problem Description:
Having two executions, it seems plugin performs an incorrect resolution of directories an sources, because in the second execution (calypso) resolves the schemaDirectory of the first one (sercom).
Attached an extract of the pom.xml file (pom.extract.txt) and a build log file (build.log)
Please notice that the schemaDirectory resolved in the second executions is wrong.
[INFO] schemaDirectory = /home/szarza/proyectos/cestel/hermes/client/src/main/bindings/sercom
build.log
pom.extract.txt
The text was updated successfully, but these errors were encountered: