classpath too long (cut)

GoogleCodeExporter commented 9 years ago

Is this Maven 1 or Maven 2?
Maven 2

What steps will reproduce the problem?
1. Make your project depend on lots different libs 
2. And you folder in depth folder hierarchy 

What is the expected output? What do you see instead?
A jar is needed for the compilation (ex: mygwt.jar if my GWT module
inherits net.mygwt.ui.MyGWT) but it is not in the classpath defined for the
GWT compilation command, so the GWT compilation fail. 
If I move my Maven repository, in the root of C:/repository (which is less
deep that C:/Documents and Settings/My Login/.m2/repository), the jar
needed appears in the classpath, so the GWT compilation succeed. 

I think this problem is related to the Issue #84. 

The real problem is that there is too many jars in the classpath, but I
only need mygwt.jar in addition to the jar of GWT-HOME (gwt-user.jar),
"target\classes" and "target/resources" of the project. 

I think the better way to resolve this is to let people specify manually
the jars they want to add to the classpath for the GWT compilation, for
example a new property in configuration : 
<plugin>
     <groupId>com.totsp.gwt</groupId>
     <artifactId>maven-googlewebtoolkit2-plugin</artifactId> 
     <configuration>
          ...
          <classpath>

          </classpath>
     </configuration>
     ...
</plugin>

I think it's the best practice because we really don't have to add the 50
or more jars to the classpath to compile a GWT module in javascript, just
the GWT libraries (mygwt, gwt-ext, gwt-dnd, ...) are needed in addition to
the gwt-user and some java.util classes. 

What version of the product are you using? On what operating system?
maven-googlewebtoolkit2-plugin on Windows XP

Please provide any additional information below.

Output with the repository in C:/Documents and
Settings/MyLogin/.m2/repository :

E:\dev\occ-workspace\occ-app-pom>"C:\bea\jdk150_04\jre\bin\java"  -cp
"E:\dev\apps\gwt-windows-1.4.61";"E:\dev\apps\gwt-windows-1.4.61\gwt-user.jar";"
E:\dev\apps\gwt-windows-1.4.61\gwt-dev-windows.jar";"E:\dev\occ-workspace\occ-we
b\src\main\java";"E:\dev\occ-workspace\occ-web\src\main\resources";"E:
\dev\occ-workspace\occ-web\src\main\configurator";"E:\dev\occ-workspace\occ-web\
classes";"E:\dev\occ-workspace\occ-web\target\classes";"C:\Documents
and
Settings\YRKA8220\.m2\repository\com\francetelecom\onecrm\configurator-gui\2.1.0
-SNAPSHOT\configurator-gui-2.1.0-SNAPSHOT.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\jboss\jboss-common-core\2.0.4.GA\jboss-common-c
ore-2.0.4.GA.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\com\francetelecom\onecrm\configurator-kernel\2.
1.0-SNAPSHOT\configurator-kernel-2.1.0-SNAPSHOT.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\axis\axis\1.4\axis-1.4.jar";"C:\Docu
ments
and
Settings\YRKA8220\.m2\repository\commons-logging\commons-logging\1.0.4\commons-l
ogging-1.0.4.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\javax\servlet\jstl\1.0.2\jstl-1.0.2.jar";"C:\Do
cuments
and
Settings\YRKA8220\.m2\repository\javax\servlet\servlet-api\2.4\servlet-api-2.4.j
ar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\asm\asm\1.5.3\asm-1.5.3.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\axis\axis-jaxrpc\1.4\axis-jaxrpc-1.4
.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\jboss\javassist\3.3.ga\javassist-3.3.ga.jar";"C
:\Documents
and
Settings\YRKA8220\.m2\repository\taglibs\standard\1.1.2\standard-1.1.2.jar";"C:\
Documents
and
Settings\YRKA8220\.m2\repository\commons-validator\commons-validator\1.3.1\commo
ns-validator-1.3.1.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\gwtwidgets\server\spring\gwt-sl\0.1.4\gwt-s
l-0.1.4.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\net\sf\ehcache\ehcache\1.2.3\ehcache-1.2.3.jar"
;"C:\Documents
and
Settings\YRKA8220\.m2\repository\javax\servlet\jsp\jsp-api\2.1\jsp-api-2.1.jar";
"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\struts\struts-extras\1.3.8\struts-ex
tras-1.3.8.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\commons-lang\commons-lang\2.3\commons-lang-2.3.
jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\com\thoughtworks\xstream\xstream\1.2.2\xstream-
1.2.2.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\springframework\spring\2.0.3\spring-2.0.3.j
ar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\cglib\cglib\2.1_3\cglib-2.1_3.jar";"C:\Document
s
and
Settings\YRKA8220\.m2\repository\asm\asm-attrs\1.5.3\asm-attrs-1.5.3.jar";"E:\de
v\occ-workspace\occ-core\target\classes";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\struts\struts-el\1.3.8\struts-el-1.3
.8.jar";"C:\Documents
and Settings\YRKA8220\.m2\
repository\org\hibernate\hibernate-annotations\3.3.0.ga\hibernate-annotations-3.
3.0.ga.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\axis\axis-wsdl4j\1.5.1\axis-wsdl4j-1.5.1.jar";"
C:\Documents
and
Settings\YRKA8220\.m2\repository\org\hibernate\hibernate-validator\3.0.0.ga\hibe
rnate-validator-3.0.0.ga.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\com\google\gwt\gwt-user\1.4.61\gwt-user-1.4.61.
jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\log4j\log4j\1.2.14\log4j-1.2.14.jar";"C:\Docume
nts
and
Settings\YRKA8220\.m2\repository\concurrent\concurrent\1.3.4\concurrent-1.3.4.ja
r";"C:\Documents
and
Settings\YRKA8220\.m2\repository\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar";"E
:\dev\occ-workspace\occ-exchange\target\classes";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\hibernate\hibernate-entitymanager\3.3.1.ga\
hibernate-entitymanager-3.3.1.ga.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\struts\struts-taglib\1.3.8\struts-ta
glib-1.3.8.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\org\apache\geronimo\specs\geronimo-jms_1.1_spec
\1.1\geronimo-jms_1.1_spec-1.1.jar";"C:\Documents
and
Settings\YRKA8220\.m2\repository\commons-chain\commons-chain\1.1\commons-chain-1
.1.jar";;
 com.google.gwt.dev.GWTCompiler  -gen
"E:\dev\occ-workspace\occ-web\target\.generated" -logLevel INFO
-style OBF -out E:\dev\occ-workspace\occ-web\target\occ-web-0.1-SNAPSHOT
com.francetelecom.occ.Configurator
Loading module 'com.francetelecom.occ.Configurator'
   Loading inherited module 'com.francetelecom.framework.gwt.hmvc.TatamiHmvc'
      [ERROR] Unable to find
'com/francetelecom/framework/gwt/hmvc/TatamiHmvc.gwt.xml' on your
classpath; could be a typo, or maybe you forgot to incl
ude a classpath entry for source?
   [ERROR] Line 5: Unexpected exception while processing element 'inherits'
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:157)
        at
com.google.gwt.dev.cfg.ModuleDefSchema$BodySchema.__inherits_begin(ModuleDefSche
ma.java:143)
        at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
com.google.gwt.dev.util.xml.HandlerMethod.invokeBegin(HandlerMethod.java:223)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.startElement(ReflectiveParser.
java:242)
        at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:
454)
        at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocu
mentParser.java:217)
        at
org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:5
94)
        at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidator.java:777
)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocume
ntFragmentScannerImpl.java:748)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.
dispatch(XMLDocumentFragmentScannerImpl.java:1453)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFr
agmentScannerImpl.java:333)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
        at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
        at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:29
5)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.ja
va:48)
        at
com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:366)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:175)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.load(ModuleDefLoader.java:208)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.java:81
)
        at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:753)
        at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:745)
        at com.google.gwt.dev.GWTCompiler.main(GWTCompiler.java:213)
   [ERROR] Failure while parsing XML
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
        at
com.google.gwt.dev.util.xml.DefaultSchema.onHandlerException(DefaultSchema.java:
56)
        at
com.google.gwt.dev.util.xml.Schema.onHandlerException(Schema.java:65)
        at
com.google.gwt.dev.util.xml.Schema.onHandlerException(Schema.java:65)
        at
com.google.gwt.dev.util.xml.HandlerMethod.invokeBegin(HandlerMethod.java:233)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.startElement(ReflectiveParser.
java:242)
        at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:
454)
        at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocu
mentParser.java:217)
        at
org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java:5
94)
        at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidator.java:777
)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocume
ntFragmentScannerImpl.java:748)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.
dispatch(XMLDocumentFragmentScannerImpl.java:1453)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFr
agmentScannerImpl.java:333)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
        at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
        at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1169)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:29
5)
        at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.ja
va:48)
        at
com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:366)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:175)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.load(ModuleDefLoader.java:208)
        at
com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.java:81
)
        at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:753)
        at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:745)
        at com.google.gwt.dev.GWTCompiler.main(GWTCompiler.java:213)
[ERROR] Build failed
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failed.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 53 seconds
[INFO] Finished at: Fri Mar 21 11:29:19 CET 2008
[INFO] Final Memory: 12M/254M
[INFO] ------------------------------------------------------------------------

Output with the repository in C:/repository :

E:\dev\occ-workspace\occ-app-pom>"C:\bea\jdk150_04\jre\bin\java"  -cp
"E:\dev\apps\gwt-windows-1.4.61";"E:\dev\apps\gwt-windows-1.4.61\gwt-user.jar";"
E:\dev\apps\gwt-windows-1.4.61\gwt-dev-windows.jar";"E:\dev\occ-workspace\occ-we
b\src\main\java";"E:\dev\occ-workspace\occ-web\src\main\resources";"E:
\dev\occ-workspace\occ-web\src\main\configurator";"E:\dev\occ-workspace\occ-web\
classes";"E:\dev\occ-workspace\occ-web\target\classes";"C:\repository\
com\francetelecom\onecrm\configurator-gui\2.1.0-SNAPSHOT\configurator-gui-2.1.0-
SNAPSHOT.jar";"C:\repository\jboss\jboss-common-core\2.0.4.GA\jboss-co
mmon-core-2.0.4.GA.jar";"C:\repository\com\francetelecom\onecrm\configurator-ker
nel\2.1.0-SNAPSHOT\configurator-kernel-2.1.0-SNAPSHOT.jar";"C:\reposit
ory\org\apache\axis\axis\1.4\axis-1.4.jar";"C:\repository\javax\servlet\servlet-
api\2.4\servlet-api-2.4.jar";"C:\repository\commons-logging\commons-lo
gging\1.0.4\commons-logging-1.0.4.jar";"C:\repository\javax\servlet\jstl\1.0.2\j
stl-1.0.2.jar";"E:\dev\occ-workspace\occ-exchange\target\classes";"C:\
repository\asm\asm\1.5.3\asm-1.5.3.jar";"C:\repository\org\apache\axis\axis-jaxr
pc\1.4\axis-jaxrpc-1.4.jar";"C:\repository\jboss\javassist\3.3.ga\java
ssist-3.3.ga.jar";"C:\repository\taglibs\standard\1.1.2\standard-1.1.2.jar";"C:\
repository\commons-validator\commons-validator\1.3.1\commons-validator
-1.3.1.jar";"C:\repository\org\gwtwidgets\server\spring\gwt-sl\0.1.4\gwt-sl-0.1.
4.jar";"C:\repository\net\sf\ehcache\ehcache\1.2.3\ehcache-1.2.3.jar";
"C:\repository\javax\servlet\jsp\jsp-api\2.1\jsp-api-2.1.jar";"C:\repository\org
\apache\struts\struts-extras\1.3.8\struts-extras-1.3.8.jar";"C:\reposi
tory\commons-lang\commons-lang\2.3\commons-lang-2.3.jar";"C:\repository\com\thou
ghtworks\xstream\xstream\1.2.2\xstream-1.2.2.jar";"C:\repository\org\s
pringframework\spring\2.0.3\spring-2.0.3.jar";"C:\repository\cglib\cglib\2.1_3\c
glib-2.1_3.jar";"C:\repository\asm\asm-attrs\1.5.3\asm-attrs-1.5.3.jar
";"C:\repository\org\apache\struts\struts-el\1.3.8\struts-el-1.3.8.jar";"C:\repo
sitory\org\hibernate\hibernate-annotations\3.3.0.ga\hibernate-annotati
ons-3.3.0.ga.jar";"C:\repository\axis\axis-wsdl4j\1.5.1\axis-wsdl4j-1.5.1.jar";"
C:\repository\org\hibernate\hibernate-validator\3.0.0.ga\hibernate-val
idator-3.0.0.ga.jar";"C:\repository\log4j\log4j\1.2.14\log4j-1.2.14.jar";"C:\rep
ository\com\google\gwt\gwt-user\1.4.61\gwt-user-1.4.61.jar";"C:\reposi
tory\concurrent\concurrent\1.3.4\concurrent-1.3.4.jar";"C:\repository\javax\tran
saction\jta\1.0.1B\jta-1.0.1B.jar";"C:\repository\org\hibernate\hibern
ate-entitymanager\3.3.1.ga\hibernate-entitymanager-3.3.1.ga.jar";"C:\repository\
org\apache\struts\struts-taglib\1.3.8\struts-taglib-1.3.8.jar";"C:\rep
ository\org\apache\geronimo\specs\geronimo-jms_1.1_spec\1.1\geronimo-jms_1.1_spe
c-1.1.jar";"C:\repository\commons-chain\commons-chain\1.1\commons-chai
n-1.1.jar";"C:\repository\antlr\antlr\2.7.6\antlr-2.7.6.jar";"C:\repository\org\
hibernate\hibernate\3.2.2.ga\hibernate-3.2.2.ga.jar";"C:\repository\co
mmons-beanutils\commons-beanutils\1.7.0\commons-beanutils-1.7.0.jar";"C:\reposit
ory\org\hibernate\hibernate-commons-annotations\3.3.0.ga\hibernate-com
mons-annotations-3.3.0.ga.jar";"C:\repository\oro\oro\2.0.8\oro-2.0.8.jar";"C:\r
epository\javax\persistence\persistence-api\1.0\persistence-api-1.0.ja
r";"C:\repository\com\francetelecom\onecrm\configurator-core\2.1.0-SNAPSHOT\conf
igurator-core-2.1.0-SNAPSHOT.jar";"C:\repository\opensymphony\sitemesh
\2.3\sitemesh-2.3.jar";"E:\dev\occ-workspace\occ-core\target\classes";"C:\reposi
tory\joda-time\joda-time\1.4\joda-time-1.4.jar";"C:\repository\org\apa
che\struts\struts-core\1.3.8\struts-core-1.3.8.jar";"C:\repository\commons-diges
ter\commons-digester\1.8\commons-digester-1.8.jar";"C:\repository\dom4
j\dom4j\1.6.1\dom4j-1.6.1.jar";"C:\repository\org\apache\axis\axis-saaj\1.4\axis
-saaj-1.4.jar";"C:\repository\com\francetelecom\clara\component\tatami
-hmvc\1.0\tatami-hmvc-1.0.jar";"C:\repository\commons-collections\commons-collec
tions\3.2\commons-collections-3.2.jar";"C:\repository\org\apache\strut
s\struts-tiles\1.3.8\struts-tiles-1.3.8.jar";; 
com.google.gwt.dev.GWTCompiler  -gen
"E:\dev\occ-workspace\occ-web\target\.generated" -logLevel INFO -
style OBF -out E:\dev\occ-workspace\occ-web\target\occ-web-0.1-SNAPSHOT
com.francetelecom.occ.Configurator
Output will be written into
E:\dev\occ-workspace\occ-web\target\occ-web-0.1-SNAPSHOT\com.francetelecom.occ.C
onfigurator
Compilation succeeded

Original issue reported on code.google.com by rudy.k...@gmail.com on 21 Mar 2008 at 10:35

GoogleCodeExporter commented 9 years ago

Original comment by charlie....@gmail.com on 25 Mar 2008 at 12:24

GoogleCodeExporter commented 9 years ago

I was not able to get 2.0-beta6 or 2.0-beta7 working on windows xp because our 
classpath was 16kb as a 
result of maven's transitive dependence and our extensive dependencies.  By 
extending the comspec to 32kb I 
was able to fix this issue.  Our other alternative was to modify the 
ScriptWriterWindows class to utilze a subst to 
reduce the length of the classpath.

Original comment by michael....@gmail.com on 26 Mar 2008 at 10:45

GoogleCodeExporter commented 9 years ago

Could you please try 2.0beta8 and let me know if the changes work for you.

Thanks.

Original comment by keber...@gmail.com on 29 Mar 2008 at 4:20

GoogleCodeExporter commented 9 years ago

It works with 2.0beta10. 
I have the same number of jars when my repository is in C:/repository or 
C:/Documents
and Setting/MyLogin/.m2/repository.

Good work, thank you very much.

Rudy

Original comment by rudy.k...@gmail.com on 31 Mar 2008 at 10:04

GoogleCodeExporter commented 9 years ago

Original comment by charlie....@gmail.com on 2 Apr 2008 at 2:42

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

please reopen as this issue as there's still a problem:

Instead of the gwt command line being too long now the command line that set's 
the
CLASSPATH environment variable is too long, see example below.

maybe it's possible to do something like this:

SET LONGCLASSPATH1=....
SET LONGCLASSPATH2=....
SET CLASSPATH1=%LONGCLASSPATH1%;%LONGCLASSPATH2%

Would appreciate a timely fix.

Here's an example of how it fails for me:

D:\data\GRT5\grt5\sops-app\sops-gwt-client>mvn clean install
[INFO] Scanning for projects...
[INFO] 
----------------------------------------------------------------------------
[INFO] Building sops-gwt-client Maven Webapp
[INFO]    task-segment: [clean, install]
[INFO] 
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory D:\data\GRT5\grt5\sops-app\sops-gwt-client\target
[INFO] Deleting directory 
D:\data\GRT5\grt5\sops-app\sops-gwt-client\target\classes
[INFO] Deleting directory 
D:\data\GRT5\grt5\sops-app\sops-gwt-client\target\test-classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading: http://maven/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading:
http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//axis/axis-jaxrpc/1.4/axis-j
axrpc-1.4.pom
Downloading: 
http://repository.jboss.com/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading: 
http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading: http://maven/axis/axis-saaj/1.4/axis-saaj-1.4.pom
Downloading:
http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//axis/axis-saaj/1.4/axis-saa
j-1.4.pom
Downloading: 
http://repository.jboss.com/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom
Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom
[INFO] [compiler:compile]
Compiling 206 source files to 
D:\data\GRT5\grt5\sops-app\sops-gwt-client\target\classes
[INFO] [gwt:compile {execution: default}]
Override:

D:\data\GRT5\grt5\sops-app\sops-gwt-client>set
CLASSPATH="D:\data\libs\gwt-windows-1.4.60";"D:\data\libs\gwt-windows-1.4
.60\gwt-user.jar";"D:\data\libs\gwt-windows-1.4.60\gwt-dev-windows.jar";"D:\data
\GRT5\grt5\sops-app\sops-gwt-client\src\
main\java";"D:\data\GRT5\grt5\sops-app\sops-gwt-client\src\main\resources";"D:\d
ata\GRT5\grt5\sops-app\sops-gwt-client\c
lasses";"D:\data\GRT5\grt5\sops-app\sops-gwt-client\target\classes";"C:\Document
s and
Settings\dominicc\.m2\repository\m
x4j\mx4j-tools\3.0.1\mx4j-tools-3.0.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\acegisecurity\acegi-securi
ty-tiger\1.0.4\acegi-security-tiger-1.0.4.jar";"C:\Documents and
Settings\dominicc\.m2\repository\poi\poi\2.5.1-final-20
040804\poi-2.5.1-final-20040804.jar";"C:\Documents and
Settings\dominicc\.m2\repository\logkit\logkit\1.0.1\logkit-1.0.1
.jar";"C:\Documents and
Settings\dominicc\.m2\repository\junit-addons\junit-addons\1.4\junit-addons-1.4.
jar";"C:\Documen
ts and
Settings\dominicc\.m2\repository\org\springframework\spring-mock\2.0.8\spring-mo
ck-2.0.8.jar";"C:\Documents
and S
ettings\dominicc\.m2\repository\org\mortbay\jetty\jetty\6.1.1\jetty-6.1.1.jar";"
C:\Documents
and Settings\dominicc\.m2\r
epository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar";"C:\Docum
ents
and Settings\dominicc\.m2\repositor
y\org\springframework\spring\2.5.2\spring-2.5.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\classworlds\clas
sworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\mav
en-repository-metadata\2.0.6\maven-repository-metadata-2.0.6.jar";"C:\Documents 
and
Settings\dominicc\.m2\repository\org
\springframework\integration\spring-integration-core\1.0.0.m2\spring-integration
-core-1.0.0.m2.jar";"C:\Documents
and Se
ttings\dominicc\.m2\repository\aspectj\aspectjrt\1.5.2a\aspectjrt-1.5.2a.jar";"C
:\Documents
and Settings\dominicc\.m2\re
pository\jboss\trove\1.0.2-brew\trove-1.0.2-brew.jar";"C:\Documents and
Settings\dominicc\.m2\repository\com\google\gwt\
gwt-user\1.4.60\gwt-user-1.4.60.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-pool\commons-pool\1.2\co
mmons-pool-1.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\maven-model\2.0.6\maven-model-
2.
0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\net\sf\dozer\dozer\4.1\dozer-4.1.jar";"C:\Docum
ents
and Sett
ings\dominicc\.m2\repository\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar";"C:\Do
cuments
and Settings\dominicc\.m2\reposi
tory\commons-lang\commons-lang\2.1\commons-lang-2.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-bean
utils\commons-beanutils\1.7.0\commons-beanutils-1.7.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\spring
framework\spring-core\2.5.2\spring-core-2.5.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\m
aven-profile\2.0.6\maven-profile-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\maven-pl
ugin-registry\2.0.6\maven-plugin-registry-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\mortbay\jett
y\jetty-management\6.1.1\jetty-management-6.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven
\maven-settings\2.0.6\maven-settings-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\javax\persistence\per
sistence-api\1.0\persistence-api-1.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\mortbay\jetty\jsp-api-2
.1\6.1.1\jsp-api-2.1-6.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\log4j\log4j\1.2.15\log4j-1.2.15.jar";
"C:\Documents and
Settings\dominicc\.m2\repository\javax\activation\activation\1.1\activation-1.1.
jar";"C:\Documents
and
 Settings\dominicc\.m2\repository\aspectj\aspectjweaver\1.5.2a\aspectjweaver-1.5.2a.jar";"C:\Documents
and Settings\domi
nicc\.m2\repository\javax\servlet\servlet-api\2.3\servlet-api-2.3.jar";"C:\Docum
ents
and Settings\dominicc\.m2\repositor
y\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\cglib\cglib-nodep\2.1_3\cglib-no
dep-2.1_3.jar";

D:\data\GRT5\grt5\sops-app\sops-gwt-client>set
CLASSPATH="D:\data\libs\gwt-windows-1.4.60";"D:\data\libs\gwt-windows-1.4
.60\gwt-user.jar";"D:\data\libs\gwt-windows-1.4.60\gwt-dev-windows.jar";"D:\data
\GRT5\grt5\sops-app\sops-gwt-client\src\
main\java";"D:\data\GRT5\grt5\sops-app\sops-gwt-client\src\main\resources";"D:\d
ata\GRT5\grt5\sops-app\sops-gwt-client\c
lasses";"D:\data\GRT5\grt5\sops-app\sops-gwt-client\target\classes";"C:\Document
s and
Settings\dominicc\.m2\repository\m
x4j\mx4j-tools\3.0.1\mx4j-tools-3.0.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\acegisecurity\acegi-securi
ty-tiger\1.0.4\acegi-security-tiger-1.0.4.jar";"C:\Documents and
Settings\dominicc\.m2\repository\poi\poi\2.5.1-final-20
040804\poi-2.5.1-final-20040804.jar";"C:\Documents and
Settings\dominicc\.m2\repository\logkit\logkit\1.0.1\logkit-1.0.1
.jar";"C:\Documents and
Settings\dominicc\.m2\repository\junit-addons\junit-addons\1.4\junit-addons-1.4.
jar";"C:\Documen
ts and
Settings\dominicc\.m2\repository\org\springframework\spring-mock\2.0.8\spring-mo
ck-2.0.8.jar";"C:\Documents
and S
ettings\dominicc\.m2\repository\org\mortbay\jetty\jetty\6.1.1\jetty-6.1.1.jar";"
C:\Documents
and Settings\dominicc\.m2\r
epository\commons-logging\commons-logging\1.1\commons-logging-1.1.jar";"C:\Docum
ents
and Settings\dominicc\.m2\repositor
y\org\springframework\spring\2.5.2\spring-2.5.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\classworlds\clas
sworlds\1.1-alpha-2\classworlds-1.1-alpha-2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\mav
en-repository-metadata\2.0.6\maven-repository-metadata-2.0.6.jar";"C:\Documents 
and
Settings\dominicc\.m2\repository\org
\springframework\integration\spring-integration-core\1.0.0.m2\spring-integration
-core-1.0.0.m2.jar";"C:\Documents
and Se
ttings\dominicc\.m2\repository\aspectj\aspectjrt\1.5.2a\aspectjrt-1.5.2a.jar";"C
:\Documents
and Settings\dominicc\.m2\re
pository\jboss\trove\1.0.2-brew\trove-1.0.2-brew.jar";"C:\Documents and
Settings\dominicc\.m2\repository\com\google\gwt\
gwt-user\1.4.60\gwt-user-1.4.60.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-pool\commons-pool\1.2\co
mmons-pool-1.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\maven-model\2.0.6\maven-model-
2.
0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\net\sf\dozer\dozer\4.1\dozer-4.1.jar";"C:\Docum
ents
and Sett
ings\dominicc\.m2\repository\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar";"C:\Do
cuments
and Settings\dominicc\.m2\reposi
tory\commons-lang\commons-lang\2.1\commons-lang-2.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-bean
utils\commons-beanutils\1.7.0\commons-beanutils-1.7.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\spring
framework\spring-core\2.5.2\spring-core-2.5.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\m
aven-profile\2.0.6\maven-profile-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\maven-pl
ugin-registry\2.0.6\maven-plugin-registry-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\mortbay\jett
y\jetty-management\6.1.1\jetty-management-6.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven
\maven-settings\2.0.6\maven-settings-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\javax\persistence\per
sistence-api\1.0\persistence-api-1.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\mortbay\jetty\jsp-api-2
.1\6.1.1\jsp-api-2.1-6.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\log4j\log4j\1.2.15\log4j-1.2.15.jar";
"C:\Documents and
Settings\dominicc\.m2\repository\javax\activation\activation\1.1\activation-1.1.
jar";"C:\Documents
and
 Settings\dominicc\.m2\repository\aspectj\aspectjweaver\1.5.2a\aspectjweaver-1.5.2a.jar";"C:\Documents
and Settings\domi
nicc\.m2\repository\javax\servlet\servlet-api\2.3\servlet-api-2.3.jar";"C:\Docum
ents
and Settings\dominicc\.m2\repositor
y\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\cglib\cglib-nodep\2.1_3\cglib-no
dep-2.1_3.jar";;"C:\Documents and
Settings\dominicc\.m2\repository\com\gr\grt5\infrastructure-services\1.0-SNAPSHO
T\infr
astructure-services-1.0-SNAPSHOT.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-fileupload\commons-file
upload\1.1.1\commons-fileupload-1.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-collections\common
s-collections\3.2\commons-collections-3.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\xml-apis\xml-apis\1.0.
b2\xml-apis-1.0.b2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\acegisecurity\acegi-security\1.0.4\acegi-secu
rity-1.0.4.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\springframework\spring-context-support\2.5.
2\spri
ng-context-support-2.5.2.jar";"C:\Documents and
Settings\dominicc\.m2\repository\aopalliance\aopalliance\1.0\aopalliance
-1.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\axis\axis\1.4\axis-1.4.jar";"C:\Documents and
Settings\domi
nicc\.m2\repository\org\springframework\spring-beans\2.5.2\spring-beans-2.5.2.ja
r";"C:\Documents
and Settings\dominicc\.
m2\repository\stax\stax-api\1.0.1\stax-api-1.0.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\codehaus\pl
exus\plexus-container-default\1.0-alpha-9-stable-1\plexus-container-default-1.0-
alpha-9-stable-1.jar";"C:\Documents
and
Settings\dominicc\.m2\repository\jboss\jboss-messaging-client\1.4.0.GA\jboss-mes
saging-client-1.4.0.GA.jar";"C:\Document
s and 
Settings\dominicc\.m2\repository\javax\jms\jms\1.1\jms-1.1.jar";"C:\Documents
and Settings\dominicc\.m2\repository
\org\codehaus\mojo\xmlbeans-maven-plugin\2.3.1\xmlbeans-maven-plugin-2.3.1.jar";
"C:\Documents
and Settings\dominicc\.m2\
repository\org\mortbay\jetty\jsp-2.1\6.1.1\jsp-2.1-6.1.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\mx4j\mx
4j\3.0.1\mx4j-3.0.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\org\apache\maven\maven-artifact-manager\2.0.
6\maven-artifact-manager-2.0.6.jar";"C:\Documents and
Settings\dominicc\.m2\repository\commons-io\commons-io\1.3.1\commo
ns-io-1.3.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\net\sf\ehcache\ehcache\1.2.3\ehcache-1.2.3.jar"
;"C:\
Documents and
Settings\dominicc\.m2\repository\ehcache\ehcache\1.2.4\ehcache-1.2.4.jar";"C:\Do
cuments
and Settings\domin
icc\.m2\repository\org\apache\maven\wagon\wagon-provider-api\1.0-beta-2\wagon-pr
ovider-api-1.0-beta-2.jar";"C:\Documents
 and
Settings\dominicc\.m2\repository\jboss\jnp-client\4.2.0\jnp-client-4.2.0.jar";"C
:\Documents
and Settings\dominicc\.
m2\repository\org\hibernate\hibernate-annotations\3.2.0.ga\hibernate-annotations
-3.2.0.ga.jar";"C:\Documents
and Setting
s\dominicc\.m2\repository\org\hibernate\hibernate\3.2.5.ga\hibernate-3.2.5.ga.ja
r";"C:\Documents
and Settings\dominicc\.
m2\repository\com\gr\grt5\infrastructure-gwt\1.0-SNAPSHOT\infrastructure-gwt-1.0
-SNAPSHOT.jar";"C:\Documents
and Setting
s\dominicc\.m2\repository\javax\mail\mail\1.4\mail-1.4.jar";"C:\Documents and
Settings\dominicc\.m2\repository\com\mockr
unner\mockrunner\0.3.1\mockrunner-0.3.1.jar";"C:\Documents and
Settings\dominicc\.m2\repository\com\google\gwt\gwt-servl
et\1.4.60\gwt-servlet-1.4.60.jar";"C:\Documents and
Settings\dominicc\.m2\repository\jboss\jbossall-client\4.2.0\jbossal
l-client-4.2.0.jar";"C:\Documents and
Settings\dominicc\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar";"C:\Document
s
and
Settings\dominicc\.m2\repository\org\apache\xmlbeans\xmlbeans\2.3.0\xmlbeans-2.3
.0.jar";"C:\Documents
and Settings\d
ominicc\.m2\repository\jboss\javassist\3.5.0.GA-brew\javassist-3.5.0.GA-brew.jar
";"C:\Documents
and Settings\dominicc\.m
2\repository\org\springframework\spring-webmvc\2.5.2\spring-webmvc-2.5.2.jar";"C
:\Documents
and Settings\dominicc\.m2\re
pository\com\gr\grt5\sops\sops-services\1.0-SNAPSHOT\sops-services-1.0-SNAPSHOT.
jar";"C:\Documents
and Settings\dominicc
\.m2\repository\ant\ant\1.6.5\ant-1.6.5.jar";"C:\Documents and
Settings\dominicc\.m2\repository\com\gr\grt5\infrastructu
re\1.0-SNAPSHOT\infrastructure-1.0-SNAPSHOT.jar";"C:\Documents and
Settings\dominicc\.m2\repository\antlr\antlr\2.7.6\an
tlr-2.7.6.jar";

D:\data\GRT5\grt5\sops-app\sops-gwt-client>The input line is too long.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failed.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Thu Apr 03 12:18:45 BST 2008
[INFO] Final Memory: 12M/35M
[INFO] ------------------------------------------------------------------------

Original comment by dominic....@gr-tech.net on 3 Apr 2008 at 11:22

GoogleCodeExporter commented 9 years ago

After having a brief look at the source i see that what happens is that when the
classpath is > 4000 characters (why 4000 btw, as the limit is 2048 on w2k and 
8192 on
xp) the script writer creates a SET command with the contents of the class path 
so far.
it then continues building a new classpath string each and then creates a SET 
command
like this: "SET CLASSPATH=%CLASSPATH%;<extra classpath>;"

my problem is when the second SET is issues xp expands the existing CLASSPATH
environment variable and still complains that it's too long.

i tried updating the source to use !'s and then started CMD using "cmd /v:on !" 
which
enables delayed expansion, but this didn't help either.

neither did using the /e option to specify a larger environment size ("cmd 
/e:32768")

according to my colleague here google provided a way to invoke the gwt compiler 
from
a java program.

perhaps the best way then is to ditch all this batch file creation and call the 
gwt
compiler directly rather than starting up a new jvm?

i'm stuck, help!

Original comment by dominic....@gr-tech.net on 3 Apr 2008 at 12:21

GoogleCodeExporter commented 9 years ago

Re-opening

Original comment by charlie....@gmail.com on 4 Apr 2008 at 11:23

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Just a comment, we had several complications back in the day when we called the
compiler directly from the plugins, pure Java, and we moved to the batch file 
thing
to alleviate those issues. Long story, but the batch file thing resolved a host 
of
other issues, so we probably need to work this out and stick with the batch 
files. 
Should be a way for us to handle this properly in Windows, part of the problem 
though
is that most of us (main contribs) don't use Windows on a regular basis.  We 
have
others helping now though, so it should get addressed in a more robust manner, 
soon.

Original comment by charlie....@gmail.com on 4 Apr 2008 at 11:25

GoogleCodeExporter commented 9 years ago

My classpath length is currently 8095, using Windows Vista SP1.
Triggered the same issue, and made the same analysis as described by comment 7. 

It seems to be possible to insert the full classpath in the line launching java 
though. Attached a modified ScriptWriterWindows.java file that works for me.

Original comment by Ives.Lan...@gmail.com on 27 Apr 2008 at 7:54

Attachments:

ScriptWriterWindows.java

GoogleCodeExporter commented 9 years ago

We're having the same problem.  It would be nice if we could specify our jars
manually in the pom file instead of assuming them just with the classpath.

Original comment by jgoldb...@gmail.com on 17 Jun 2008 at 4:49

GoogleCodeExporter commented 9 years ago

I will look at adding the attached modified script writer for Windows.  

As to "it would be nice if we could specify our jars manually," that's missing 
the
point I think.  You can specify the jars manually, but at compile and shell 
time the
NATIVE code that GWT requires has to be parallel to the JARS - that's why we use
either the "automatic" mode to expand GWT somewhere, or require a
"maven.googlewebtoolkit.home" property - and then use that stuff for the 
scripts.

Original comment by charlie....@gmail.com on 1 Jul 2008 at 6:20

GoogleCodeExporter commented 9 years ago

We've come up against the same problem, and have come up with an alternative 
solution
that removes the classpath length limit completely. But it's a bit more 
complicated -
it uses Classworlds to load the classpath from a file. I've attached the source 
here
for consideration for inclusion in the project.

The fix involves:
1. The scripts written by ScriptWriterWindows are changed to use Classworlds to
launch the GWT tasks. This allows us to write the classpath to a file instead of
passing it on the command line. I've attached a patch against the current HEAD,
maven-googlewebtoolkit2-plugin-classworlds.diff. 

2. Hosted Mode's embedded Tomcat server uses the System classloader instead of 
the
Thread Context classloader, causing it to bypass the Classworlds configuration.
Instead of patching GWT directly for this, I've made a separate jar that the
maven-googlewebtoolkit2-plugin merges into the Classworlds classpath. The 
source for
this is attached as gwt-dev-classworlds.zip.

3. Classworlds contains a bug whereby paths with spaces are not handled 
correctly,
which causes problems because the default Maven repository path on Windows is 
under
"C:\Documents and Settings". So I have had to patch the current Classworlds 
HEAD to
fix this bug. The attached patch CLASSWORLDS-21.diff applies to the code at
http://svn.codehaus.org/classworlds/trunk/classworlds.

The patch to the maven plugin adds new configuration:
1. classworldsGroupId, classworldsArtifactId, classworldsVersion, and
classworldsType: These default to classworlds:classworlds:1.2-SNAPSHOT:jar which
corresponds to the version of classworlds built with the attached 
CLASSWORLDS-21.diff.

2. gwtClassworldsGroupId, gwtClassworldsArtifactId, gwtClassworldsVersion,
gwtClassworldsType: These default to com.infocomp:gwt-dev-classworlds:1.5.0:jar 
which
corresponds to jar built from the attached gwt-dev-classworlds.zip.

Original comment by pfelt...@infocomp.com on 14 Jul 2008 at 12:57

Attachments:

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Just adding a note to this issue that details how the Surefire plugin deals 
with this
problem:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/class-loading.htm
l. 

Not saying we should do any of that (in fact I know that doesn't work in some 
GWT
scenarios where GWT inspects the classpath itself - like JUnitShell), just 
throwing
it in the discussion to note ways that others have dealt with this.

Original comment by charlie....@gmail.com on 3 Sep 2008 at 11:34

GoogleCodeExporter commented 9 years ago

I tried with latest plugin and comment 10 solution, nothing works out. I 
attached 
the plugin configuration and log.

Original comment by mallik.a...@gmail.com on 5 Sep 2008 at 8:45

Attachments:

plugin-error.txt

GoogleCodeExporter commented 9 years ago

I think we are going to have to go the Classworlds route, but to be honest I am 
not
excited about having to do that. 

Are there any Windows people that want to become project members who are 
willing to
take this on and implement and support it?

Original comment by charlie....@gmail.com on 17 Sep 2008 at 2:55

GoogleCodeExporter commented 9 years ago

Forgot to say, thanks for the patches on this thread, they are all really 
useful in
figuring out what's up and deciding how to address it - regardless of which we
ultimately use.  (And the classworlds one looks great to me, but don't have the 
time
or will to implement and test it right now - hence looking for contributors.)

Original comment by charlie....@gmail.com on 17 Sep 2008 at 2:57

GoogleCodeExporter commented 9 years ago

Hello All,
  I had same problem and the horror is full,I am trying all workarounds and nothing 
is working.I tried to subst the path to the repo but this also is not 
working.Help.
Pavel

Original comment by pavelto...@gmail.com on 19 Sep 2008 at 5:33

GoogleCodeExporter commented 9 years ago

We have appreciate all work done till now and congratulations for it. We 
experience 
same problem with too long path which cannot be solved at all. Any workarounds 
are 
welcomed we tried the recipes but they do not help. Any help is appreciated.

IV Team

Original comment by infinite...@gmail.com on 19 Sep 2008 at 6:22

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Hello All,

  I have managed the problem with following steps under windows XP
  1. Open cmd and execute command "subst M: /path/to/repository". Note your repo is 
for example at D:\Maven2.0.9\repo it is good to subst M: D:\Maven2.0.9 The 
reason for 
this is that if you subst it to D:\Maven2.0.9\repo you will get an error when 
generating eclipse project, in this case the first letter is missing so call 
"subst 
M: D:\Maven2.0.9
  2. In settings.xml put <localRepository>M:/repo</localRepository>
  3. Set enviroment variable "set M2_REPO=M:/repo"

Best Regards,
Pavel Tonev

Original comment by pavelto...@gmail.com on 20 Sep 2008 at 11:33

GoogleCodeExporter commented 9 years ago

Hi All,

My team and I have been eagerly awaiting a fix to this problem but since since 
we 
haven't heard anything in a while we decided to try the classworlds patch 
ourselves.  

It works great.  

The source has changed a bit since the classworlds patch was posted, but 
overall it 
wasn't too hard to integrate into the current branch.

Charlie, let me know if you want any help patching the code.

Thanks,

Garey

Original comment by garey.ta...@gmail.com on 28 Oct 2008 at 5:31

GoogleCodeExporter commented 9 years ago

I can't managed to use the classworlds fix.

I got problems with the gwt-dev-classworlds.zip which do not work any more.

Please help !

Original comment by cyril.la...@gmail.com on 5 Nov 2008 at 10:28

GoogleCodeExporter commented 9 years ago

If you want, I can send you a zip with all the files you need.  In my version I 
did 
not fix the Windows "path with spaces" error (I was lazy).

-g

Original comment by garey.ta...@gmail.com on 7 Nov 2008 at 3:43

GoogleCodeExporter commented 9 years ago

First, I want to thank pfelt...@infocomp.com who made this patch.  All I have 
done is 
update his patch for the current version of gwt-maven.

I've attached a zip file that contains two eclipse projects.  If you have maven 
installed on your system you should be able to unzip and just run "mvn install" 
in 
each of the projects.

You will then need to update your pom to use this new version of the gwt-maven 
plugin:
<version>2.0.1-beta24-SNAPSHOT</version>

Please forgive my versioning; I had no idea what to set it as.

Also, this patch defaults to GWT version 1.5.3

That's about it.

-g

Original comment by garey.ta...@gmail.com on 7 Nov 2008 at 4:27

Attachments:

gwt-maven-classworlds.zip

GoogleCodeExporter commented 9 years ago

Thanks! We had worked around this problem by shortening our path to the local
repo...but just a few hours ago this issue reared it's ugly head again due to 
some
new deps that were added. Thanks so much for posting this...you've saved me 
quite a
few hairs!

Original comment by patrick.jaromin on 7 Nov 2008 at 7:50

GoogleCodeExporter commented 9 years ago

More info: 
http://groups.google.com/group/gwt-maven/browse_thread/thread/3355aa34711ee085

Still no real "owner" for this though, volunteers welcome.

Original comment by charlie....@gmail.com on 10 Nov 2008 at 1:49

GoogleCodeExporter commented 9 years ago

I put together a slightly different solution, which works for me.  I didnt like 
the
idea of relying on a special artifact in order to get hosted mode working, so I
modified the plugin to use bash (from Cygwin) if its installed.  This probably 
isnt
any cleaner that the existing classworlds solution, but I prefer it over the 
artifact
because all of the developers on my team already have cygwin installed anyway.

To use it, simply build/compile/deploy the plugin based on the attach patch, 
then
ensure that your cygwin bin directory is on your Windows Path (for me it is
"C:\cygwin\bin").  After that, everything seems to be working as it does when
building on unix.

There are no guarantees with this solution :)  I put it together quickly and 
didnt
even properly handle Exceptions (they are dumped to stderr, and thats it), so if
someone wants to put more polish on it, go for it.

Let me know if you have any troubles.

Oh, the diff was created against trunk code, on 2009.01.07

Original comment by ssenecal...@gmail.com on 8 Jan 2009 at 2:40

Attachments:

cygwin_bash.diff

GoogleCodeExporter commented 9 years ago

We also do not have a solution to the problem. 
Cygwin workaround patch seems promising. Can it be integrated into
gwt-maven? The behaviour can be made configurable so the patch will
not break any backward compatibility...

Thanks

Original comment by mgrushin...@gmail.com on 20 Jan 2009 at 2:51

GoogleCodeExporter commented 9 years ago

You people can't fix something and integral as a classpath issue in 8 
months!!!!!!

Original comment by andre.bo...@gmail.com on 2 Feb 2009 at 11:47

GoogleCodeExporter commented 9 years ago

The workaround I posted (#26) has been working fine for us.

Original comment by garey.ta...@gmail.com on 2 Feb 2009 at 11:53

GoogleCodeExporter commented 9 years ago

Which version of the plugin has patch from post #26?
We have beta24 and it is still not fixed there.

Thanks

Original comment by mgrushin...@gmail.com on 3 Feb 2009 at 3:58

GoogleCodeExporter commented 9 years ago

I do not believe that the #26 patch was ever moved into the actual plugin.  
After 
post #28 I figured that the people in charge wanted to go a different route.  
That 
route didn't work for me or my org.  

So, if you're running into the classpath issue, I recommend that you follow 
#26.  
It's what we're using in my organization and it's pretty much fixed all of our 
issues.  

I'm pretty sure everything will change with the gwt 1.6 release, so until then 
use 
the #26 fix.  ie. download the zip, run maven install, update poms.

Hope this helps,

-g

Original comment by garey.ta...@gmail.com on 3 Feb 2009 at 4:38

GoogleCodeExporter commented 9 years ago

We already use SNAPSHOT since a few mounts with this plugin, and to solve an 8
mounths issues we have to use a patched SNAPSHOT version ???

Sorry, but we are coding application that will go in production, and that sounds
strange to use such a patched SNAPSHOT version...

What about a release with this patch ?

Original comment by cyril.la...@gmail.com on 11 Feb 2009 at 9:28

GoogleCodeExporter commented 9 years ago

Please integrate the patch from post #26. It is the only solution which fixed
the issue for us. Other approaches simply didn't work.
Thanks,
--MG

Original comment by mgrushin...@gmail.com on 21 Feb 2009 at 8:40

GoogleCodeExporter commented 9 years ago

I'd like to know what's going on with the gwt-maven & codehaus merger:
http://groups.google.com/group/Google-Web-Toolkit-
Contributors/browse_thread/thread/72cf8810759c7c3

In the case of this plugin/issue my team has had to update our version again 
for gwt 
1.6. All the hosted mode and compiler commands were changed.  We also fixed an 
issue 
we were having with parent pom dependencies not building the classpath 
correctly.

If it's working error free I can post if here if you want.  I don't have the 
time to 
merge with the current branch and I'm not sure if it's even worth it because of 
the 
merger.

-g

Original comment by garey.ta...@gmail.com on 22 Feb 2009 at 12:19

GoogleCodeExporter commented 9 years ago

Please, integrate patch from post #26.

Note: while using patch from post #26, I encounter warning, see attachement.

Original comment by jspe...@gmail.com on 17 Mar 2009 at 1:50

Attachments:

warning.txt

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

One of the fix to the problem of "GWT compilation fails due to- The input line 
is 
too long." is as follows:
1) Change m2(maven) repository.
  You might have your maven repository at:
      C:\Documents and Settings\MahcineNameABC\.m2
  Copy settings.xml file from folder "apache-maven-2.0.8\apache-maven-2.0.8\conf"
  into C:\Documents and Settings\MahcineNameABC\.m2

  In settings.xml, change the tag as 
     <localRepository>M:</localRepository>
  Now your m2 home is a virtual M drive.
2) Create a repository folder as "D:\maven-2.0.8\repository"
3) Cut/Copy all the files/folders from "C:\Documents and 
Settings\MahcineNameABC\.m2
\repository"
   to "D:\maven-2.0.8\repository"
4) Map local drive: open command prompt and execute (to create the virtual 
drive):
    subst M: D:\maven-2.0.8\repository
   Now a virtual M drive will point to your repository.
5) Set environment variable M2_REPO with value M:
6) To enable long inputs, on command prompt execute:
    cmd /e:32768
This would fix the problem of long inputs due to very long entries in classpath 
variables, atleast in Win XP SP2. The inputs are combined and tested from 
comment#22 
and #7.

Hope it helps!

-Gaurav Ashwin

Original comment by gaurav.a...@gmail.com on 24 Mar 2009 at 6:22

GoogleCodeExporter commented 9 years ago

Excellent point from Gaurav _ will add that to the FAQ. 

Beyond that we aren't going to make further changes here - this plugin will be 
frozen
soon and work will begin on validating and supporting the same features at the
Codehaus Mojo GWT plugin project.  They claim to have already solved this issue 
there
(will need to validate, will re-open if necc there - not here).

Original comment by charlie....@gmail.com on 30 Mar 2009 at 4:01

Changed state: WontFix

GoogleCodeExporter commented 9 years ago

Thanks for the update on the Codehaus merger.  Regarding Gaurav, that solution 
only 
works for a short period of time.  As your project gets larger, that solution 
will 
fail.  It lasted about two weeks for us. #26 is the only one that's worked 
consistently.

Again, thanks for the update.

-g

Original comment by garey.ta...@gmail.com on 30 Mar 2009 at 5:41

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

be careful with the comspec /e switch!

I just ran into a problem that was caused by adding the /e swtich to my comspec.
after that several batch scripts didn't work any longer - in fact using the 
pipe (|)
didn't work any longer on the command line (WinXP SP3):
http://support.microsoft.com/?scid=kb%3Ben-us%3B164545&x=10&y=11

Original comment by martin.t...@gmail.com on 10 Apr 2009 at 1:33

GoogleCodeExporter commented 9 years ago

I'm newbie in gwt and maven. I use windows xp. once i compile my project with 
maven-
googlewebtoolkit2-plugin 2.0-beta26, i get the long input line error. I tried 
to 
modify my pom.xml according to #26...but still not work. This error's come to 
me 
since I added dependency Axis2 into my pom.xml
Is there other ways to solve this problem?

Original comment by netty...@gmail.com on 11 Jun 2009 at 7:24

GoogleCodeExporter commented 9 years ago

I now this is an old thread; but for others searching for a solution please see 
http://blog.athico.com/2014/06/compiling-gwt-applications-on-windows.html

Original comment by michael....@gmail.com on 28 Jun 2014 at 6:50

saiddfhi / gwt-maven

classpath too long (cut) #88