[
https://issues.jboss.org/browse/JBWS-3824?page=com.atlassian.jira.plugin....
]
R Searls commented on JBWS-3824:
--------------------------------
I found this [1] description of what SureFire is doing with, a pathing jar solution, See
section, "Manifest-Only Jar". SureFire provides a configuration property,
useSystemClassLoader,
for enabling and disabling this. Do you want a similar option provided in our plugin as
well?
[1]
http://docs.codehaus.org/display/MAVENUSER/Classloading+and+Forking+under...
So then the wsprovide cmd line we would generate would look something like this
java2ws -s /home/rsearls/projects/jbws3824/target/wsprovide/java
-classdir /home/rsearls/projects/jbws3824/target/classes
-d /home/rsearls/projects/jbws3824/target/wsprovide/resources
-verbose -wsdl
-cp SOME.jar
-wrapperbean -createxsdimports
org.jboss.test.ws.plugins.tools.wsprovide.TestEndpoint
"Input line is too long" when running wsprovide in fork
mode on Windows
-----------------------------------------------------------------------
Key: JBWS-3824
URL:
https://issues.jboss.org/browse/JBWS-3824
Project: JBoss Web Services
Issue Type: Bug
Components: jaxws-tools-maven-plugin
Affects Versions: jbossws-jaxws-tools-maven-plugin-1.1.2.Final
Reporter: Alessio Soldano
Assignee: R Searls
When running the tools in fork mode on Windows OS, we can end up building a command line
which is too long.
We should prevent this by using a pathing jar solution, similarly to what Surefire plugin
does (a jar with manifest pointing to the actual dependency jars).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)