[
http://jira.codehaus.org/browse/MGWT-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245859#action_245859
]
Brian Reilly commented on MGWT-247:
-----------------------------------
Just came across MGWT-219 and
http://code.google.com/p/google-web-toolkit/issues/detail?id=5290. Ugh, what a
mess! It's a shame that Google didn't learn from Sun's mistake.
Fortunately, I think I can work around this at the moment by specifying
xercesImpl as "provided". I can only get away with that because my UiBinder
code is in a separate module that is a WAR overlay on top of the actual
deployed webapp, which includes xercesImpl.jar (2.6.2). However, this is far
from a universal solution.
I understand not wanting to put classpath hacks in the plugin, but it actually
makes for an unstable experience in the current state. Couldn't the plugin
check the GWT version, understand the packages that gwt-dev.jar bundles, and
selectively apply these hacks? That should work for current versions and also
allow for future versions of GWT to correct themselves as well. The current
plan relies on Google changing how they bundle dependencies, and there's no
timeline for that or even any guarantee that that will ever happen.
> plugin dependencies aren't resolved as expected
> -----------------------------------------------
>
> Key: MGWT-247
> URL: http://jira.codehaus.org/browse/MGWT-247
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Brian Reilly
>
> Dependencies specified within a plugin configuration are not used when the
> plugin performs actions, such as GWT compilation. For example:
> {code:xml}
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>gwt-maven-plugin</artifactId>
> <version>2.1.0</version>
> <executions>...</executions>
> <dependencies>
> <dependency>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> <version>2.9.1</version>
> <scope>compile</scope>
> </dependency>
> </dependencies>
> </plugin>
> {code}
> I'm working in a legacy project that, for other reasons (that I unfortunately
> don't understand but cannot change), is using xercesImpl version 2.6.2. This
> seems to work fine when the application is deployed, but does not work for
> compiling UiBinder .ui.xml files, as discussed here:
> http://groups.google.com/group/google-web-toolkit/browse_thread/thread/992210a7cfac2ec4.
> As it stands now, my projects specification of version 2.6.2 is being picked
> up and used during GWT compilation.
> My suspicion is that xerces 2.9.1 is needed during compilation but not
> necessarily at runtime (possibly by the GWT development mode shell, but not
> in the necessarily in the webapp it runs).
--
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
