Closed glassfishrobot closed 11 years ago
Reported by lkh007
predatorvi said: I am seeing this as well. Our Jenkins_CI server job names are something like "myproject (currentbranch)".
If I use jaxws-maven-plugin v2.1, it works fine. If I switch to jaxws-maven-plugin v2.2.1, it fails unless I change the job name to something without a space so something has changed in how the plugin passes command-line args to wsimport maybe?
@lukasj said: confirmed, fixing...
hjohn said: Is there any chance we could see a 2.3.1 release with this issue fixed? It's been almost a year since 2.3 and this bug is hitting us still forcing us to run this plugin from a path without spaces.
We cannot downgrade to 2.2 as other plugins stop working then.
zeiss said: Would you please consider making a 2.3.1 release? It is not good to have the plugin failing in such a basic scenario.
zeiss said: Is it also possible to backport the fix to 2.2 line? I cannot use 2.3 in some builds for various reasons.
This issue was imported from java.net JIRA JAX_WS_COMMONS-113
Marked as fixed on Wednesday, August 7th 2013, 5:55:29 am
[INFO] jaxws:wsimport args: [-keep, -s, D:\My Documents\SVN\app_layer\working\app_layer\src\main\java, -d, D:\My Documents\SVN\app_layer\working\app_layer\target\classes, -Xnocompile, "file:/D:/My%20Documents/SVN/app_layer/working/app_layer/src/main/resources/META-INF/wsdl/SomeService.wsdl"] directory not found: D:\My
Environment
Windows
Affected Versions
[2.3]