[
http://jira.codehaus.org/browse/MGWT-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209255#action_209255
]
Ryan Heaton commented on MGWT-168:
----------------------------------
Sure.
My specific case is that I've got some configuration files that are loaded from
the classpath. They sit in a directory on the filesystem and therefore can't be
declared as a standard maven dependency. (I actually don't want them as a
standard Maven dependency because I use different files when running in a
development environment than will be used in a production environment.) I want
this directory on the classpath when I invoke GWT DevMode, but I have no way of
accomplishing this with gwt-maven-plugin 1.2.
Thanks-
-Ryan
> provide the capability to support additional classpath entries
> --------------------------------------------------------------
>
> Key: MGWT-168
> URL: http://jira.codehaus.org/browse/MGWT-168
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Ryan Heaton
> Attachments: gwt-module-additional-entries.diff
>
>
> It would be nice to be able to specify any additional classpath entries that
> should be prepended to the the classpath when invoking a gwt shell (compile,
> devmode, etc.)
> Please apply the attached patch.
--
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