Closed JulienHoullier closed 6 years ago
Any updates on that?
I got the same issue on a Jenkins istance.
[DEBUG] Source directories: [/var/lib/jenkins/jobs/project/workspace/foo/bar/src/main/java /var/lib/jenkins/jobs/project/workspace/foo/bar/target/generated-sources/jaxb /my/mount/jenkins/jobs/projects/workspace/foo/bar/target/generated-sources/jaxb]
where /var/lib/jenkins
is a symlink to /my/mount/jenkins
. No output directory specified in the pom.xml.
Interesting point: the build runs fine when executing the mvn command manually in the same container (workspace not cleaned after failure).
Also runs fine when there is no symlink present, so I'd suspect the problem,
Did I miss any flag to prevent that issue or is this indeed a bug?
It seems that the plugin does not handle symlinks properly here (i.e. regards the symlinked directory in the same way as a non-symlinked one).
Does the same issue persist in version 2.4?
Does the same issue persist in version 2.4?
Apparently not :+1: Just compiled a minimal test example that fails using 2.3.1, but succeeds with 2.4. Thanks for that!
I guess it has been fixed with #56, right?
Indeed.
Issue on version 2.3.1, no issue on version 2.2
This issue happens on our Jenkins CI plateform, The runner try to build project files which where on /var/jenkins/workspace/ . The workspace directory is a link to a mounted directory shared by Runners /u/jenkins
On our pom.xml the xjc goals confiuration is :
where xsd.dir is set to:
And with -X logs XJC trace:
I suspect here that either ${project.build.directory} is not resolved properly, or relative src/main/resource/xsd is not resolved the same as ${basedir}/src/main/resources/xsd
Then on later compile phase trace with -X:
The last two folder are in fact the same, which leads to compilation errors: