Issue 67 in gwt-tooling: Duplicated entries in classpath causing it exceed the limit for Windows environment
codesite...@google.com
Owner: ----
New issue 67 by changyi.mao: Duplicated entries in classpath causing it
exceed the limit for Windows environment
http://code.google.com/p/gwt-tooling/issues/detail?id=67
What steps will reproduce the problem?
1. Right-click a GWT Moodule, select "GWT Tooling"->Compile and Publish
What is the expected output? What do you see instead?
Expecting to see it compiles and publishs the GWT Moodule.
But instead it gives exception:
java.io.IOException: Cannot run program "C:\Java\jdk1.6.0_11\bin\javaw.exe"
(in directory "C:\CMS\cms_portal_main\bin.gwt"): CreateProcess error=87,
The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown
Source) at java.lang.Runtime.exec(Unknown Source) at
org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:798)
at org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRunner.java:70)
at
org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:317)
at
org.eclipseguru.gwt.core.builder.GwtProjectPublisher.compileModule(GwtProjectPublisher.java:288)
at
org.eclipseguru.gwt.core.builder.GwtProjectPublisher.publishAndCompileModules(GwtProjectPublisher.java:419)
at
org.eclipseguru.gwt.core.builder.GwtProjectPublisher.runInWorkspace(GwtProjectPublisher.java:558)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: CreateProcess error=87, The parameter is
incorrect at java.lang.ProcessImpl.create(Native Method) at
java.lang.ProcessImpl.<init>(Unknown Source) at
java.lang.ProcessImpl.start(Unknown Source) ... 10 more
-----------------------------------------------------------
What version of the product are you using? On what operating system?
Windows XP Pro Edition
Eclipse EE 3.4.1
JDK 1.6
GWT Tooling 1.5.7.200901141404
Please provide any additional information below.
I traced down the code through debugging, it turns out that duplicated
entries in classpath causing it exceed the limit for Windows environment.
Because my GWT module has dependency on JBoss RunTime (which has almost 250
jar files), and other 2 modules, which in turn has dependency on JBoss
RunTime. Since the duplicates are not removed when calculating the
classpath, it ends up with more than 750 entries in the classpath, which
somehow exceeds the Window's limit(I'm not sure exactly what the threshold
is). Buy remove the duplicates, it solved the problem. Please see attached
code, between line 239 to 242 is my addition.
Attachments:
GwtProjectPublisher.java 21.3 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Status: Wontfix
Comment #1 on issue 67 by eclipseguru: Duplicated entries in classpath
causing it exceed the limit for Windows environment
http://code.google.com/p/gwt-tooling/issues/detail?id=67
We rely on "JavaRuntime#computeDefaultRuntimeClassPath" to return the
correct
classpath. If duplicates are returned than either (a) something on your
classpath is
adding those duplicate entries or (b) the method in JDT we use is broken. I
suspect
it's issue (a). Thus, please get in contact with the vendor of your JBoss
tooling/IDE.
On a side note, a GWT module should verly likely *not* depend on JBoss
Runtime. You
might want to refactor your project layout. For example, the module could
be in a
project with only GWT dependencies. The RPC service implementations can be
placed in
the larger project. That might be an interesting topic for the newsgroup.