[
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237075#action_237075
]
Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 3:22 AM:
----------------------------------------------------------------
Reopening: In the Eclipse and IntelliJ plugin we can set the order of the
entry's in the classpath given to the gwt compiler process. Having that same
ability in the maven gwt plugin will allow us to use this plugin instead of an
ant build (and get rid all the trouble the ant build represents).
Even though you're right that the gwt classpath is a mess (mixing client and
server side classpaths and whatnot), it doesn't look like they'll fix it
anytime soon, so please reconsider supporting the same feature as the Eclipse
and IntelliJ plugin to at least have some control over the gwt compiler
classpath.
Also note that both the eclipse and the intellij plugin, by default, put the
gwt-dev dependency first, not last.
was (Author: ge0ffrey):
Reopening: In the Eclipse and IntelliJ plugin we can set the order of the
entry's in the classpath given to the gwt compiler process. Having that same
ability in the maven gwt plugin will allow us to use this plugin instead of an
ant build (and get rid all the trouble the ant build represents).
Even though you're right that the gwt classpath is a mess (mixing client and
server side classpaths and whatnot), it doesn't look like they'll fix it
anytime soon, so please reconsider supporting the same feature as the Eclipse
and IntelliJ plugin to at least have some control over the gwt plugin.
Also note that both the eclipse and the intellij plugin, by default, put the
gwt-dev dependency first, not last.
> In gwt:compile the gwt-dev library should be on the classpath before the
> project dependencies
> ---------------------------------------------------------------------------------------------
>
> Key: MGWT-219
> URL: http://jira.codehaus.org/browse/MGWT-219
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Geoffrey De Smet
> Priority: Critical
>
> When compiling drools-guvnor with gwt:compile I does this:
> ...java -Xmx512m -classpath
> "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/src/main/java":
> "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/src/main/resources":
> "/home/ge0ffrey/projects/jboss/drools/drools-guvnor/target/classes":
> ...
> "/home/ge0ffrey/.m2/repository/org/eclipse/jdt/core/compiler/ecj/3.5.1/ecj-3.5.1.jar":
> ...
> "/home/ge0ffrey/.m2/repository/com/google/gwt/gwt-dev/2.0.4/gwt-dev-2.0.4.jar"
> com.google.gwt.dev.Compiler ...
> The problem is that both the gwt-dev jar and the jdt-core:ecj jar have the
> ecj classes in their jar.
> Even worse, gwt-dev 2.0.4 does not work with ecj 3.5.1.
> If the gwt-dev is first on the classpath, the compile would work (now it
> fails with a NoSuchFieldError).
> Of course if any if the client classes would use jdt, this would be a problem
> (which isn't the case)...
> See
> http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
> http://code.google.com/p/google-web-toolkit/issues/detail?id=4479
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
