[
http://jira.codehaus.org/browse/MGWT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177161#action_177161
]
Mark Renouf commented on MGWT-77:
---------------------------------
I'm not sure what happened up but now "provided" scope dependencies are being
excluded from the Hosted mode classpath.
We use "provided" to keep GWT library source JARs from going into the
WEB-INF/lib. Is there a better/different way (As the description seems to imply
that scope "runtime" does this, but that's not my understanding).
I guess a quick temporary workaround is to change all scope "provided" to scope
"compile"?
> gwt:run does not use the 'runtime' scope's classpath.
> -----------------------------------------------------
>
> Key: MGWT-77
> URL: http://jira.codehaus.org/browse/MGWT-77
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Gabe
> Assignee: nicolas de loof
> Fix For: 1.1
>
>
> I have a war project with several dependencies in the "runtime" scope.
> If I build the .war and run it in an application server, it works perfectly.
> If I run the project using gwt:run (hosted mode), the embedded Tomcat
> complains that classes on the 'runtime' scope are not present. Switching all
> runtime-only dependencies to the 'compile' scope solves the problem.
> This is suboptimal and results in a number of dependencies being included in
> the .war that should not be there.
> I'm solving this using a hosted-mode profile for the moment.
--
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
