[
http://jira.codehaus.org/browse/MGWT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237085#action_237085
]
Geoffrey De Smet edited comment on MGWT-219 at 10/1/10 10:15 AM:
-----------------------------------------------------------------
Attached patch to set gwt-dev library first on the classpath given to the GWT
compiler.
Justification:
- The Eclipse and IntelliJ plugin do this too and the default behavior of the
maven plugin, the eclipse and the IntelliJ plugin should not differ.
- Without this patch, none of the projects that depend on GWT and JDT (directly
or indirectly) can be build with this maven plugin. This includes but is not
limited to: drools-guvnor, all projects that depend on drools-guvnor (this is
extended a lot in-house), jasperreporst in a gwt app, ...
- This has been a long standing issue with the gwt-maven plugins:
http://code.google.com/p/gwt-maven/issues/detail?id=79
was (Author: ge0ffrey):
Attached patch to set gwt-dev library first on the classpath given to the
GWT compiler.
Justification:
- The Eclipse and IntelliJ plugin do this too and the default behavior of the
maven plugin, the eclipse and the IntelliJ plugin should not differ.
- Without this patch, none of the projects that depend on GWT and JDT (directly
or indirectly) can be build with this maven plugin. This includes but is not
limited to: drools-guvnor, all projects that depend on drools-guvnor (this is
extended a lot in-house), ...
- This has been a long standing issue with the gwt-maven plugins:
http://code.google.com/p/gwt-maven/issues/detail?id=79
> 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
> Attachments: MGWT-219.patch
>
>
> 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
