[
https://issues.jboss.org/browse/JBWS-3955?page=com.atlassian.jira.plugin....
]
Jan Blizňák updated JBWS-3955:
------------------------------
Workaround Description: Run the testsuite as close to filesystem root as possible, eg.
from /tmp, but it is not reliable and definitely a proper solution (was: Run the
testsuite as close to filesystem root as possible, eg. from /tmp)
JBossWS testsuite failure on Windows - CreateProcess error=206, The
filename or extension is too long
-----------------------------------------------------------------------------------------------------
Key: JBWS-3955
URL:
https://issues.jboss.org/browse/JBWS-3955
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Environment: Windows
Reporter: Jan Blizňák
Assignee: Alessio Soldano
When running whole jbossws-cxf testsuite on windows node, it fails on executing ant task
because of long classpath.
{code:java}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(wsconsume) on project jbossws-cxf-shared-tests: An Ant BuildException has occured: The
following error occurred while executing this line:
[ERROR]
W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:41:
The following error occurred while executing this line:
[ERROR]
W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\scripts\antrun-wsconsume.xml:72:
java.io.IOException: Cannot run program
"W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\jdk1.8.0.unlimited.BC\jre\bin\java.exe":
CreateProcess error=206, The filename or extension is too long
[ERROR] around Ant part ...<ant antfile="scripts/antrun-wsconsume.xml"
target="wsconsume"/>... @ 10:67 in
W:\workspace\eap-7x-jbossws-testsuite-windows\59544db6\build\stack-cxf\modules\testsuite\shared-tests\target\antrun\build-main.xml
[ERROR] -> [Help 1]
{code}
Incorporating this [
task|https://ant.apache.org/manual/Tasks/manifestclasspath.html] in
ant script might be a way how to workaround this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)