-
Notifications
You must be signed in to change notification settings - Fork 9
jaxws-maven-plugin - wsimport didn't respect symlinks #122
Comments
Reported by henri_gomez |
[email protected] said:
In contrast to other executions of goal "wsimport" the extract above uses another argument bindingDirectory than the default. This is the only execution that fails to build with Maven 3.2.2 and JDK6, while 5 other executions run successfully. |
[email protected] said: Submitting the patch (to version 2.3) as part of the comment because attachments are not enabled:
|
vojtech_k said:
|
didierl said: The strangest thing is that there was no issue when building from the command line. BTW, this issue might be related to JAX_WS-1147. |
This issue was imported from java.net JIRA JAX_WS_COMMONS-122 |
This is still an issue even in the latest 4.0.0 version. The build only seems to fail when run in Jenkins. /home/bld is a symlink to /app1/home/bld. We tried the suggestion above of setting the custom workdir, but it didn't fix it. 20:51:29 [INFO] --- jaxws-maven-plugin:4.0.0:wsimport (SubmissionService) @ services-client --- |
Hi all
I encountered a nasty problem with jaxws-maven-plugin 2.3 while doing wsimport :
plugin complains about /media/ext4/mycorp/cijenkins/jobs/jaxws-issue/workspace/src/main/resources/EPCglobal-epcis-masterdata-1_0.xsd" not a part of this compilation, expecting /var/lib/mycorp/cijenkins/jobs/jaxws-issue/workspace/src/main/resources/EPCglobal-epcis-masterdata-1_0.xsd
/var/lib/mycorp/cijenkins is a symlink to /media/ext4/mycorp/cijenkins
It seems file comparaison is using AbsolutePath instead of CanonicalPath.
Environment
openSUSE 12.2, Java 7u45, Maven 3.0.5
Affected Versions
[2.3]
The text was updated successfully, but these errors were encountered: