[
http://jira.codehaus.org/browse/MGWT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269889#action_269889
]
Thomas Broyer commented on MGWT-277:
------------------------------------
[~ge0ffrey]: depending on how your build is setup, you can, as a workaround,
easily exclude WEB-INF/deploy from your artifact.
For instance, I use the maven-assembly-plugin to create a ZIP (later used as a
WAR overlay in another module) and simply added an
<excludes><exclude>WEB-INF/deploy/**</exclude></excludes> to my assembly
descriptor.
If you use the maven-war-plugin (which seems to be the case for Guvnor), you
can set its packagingExcludes parameter.
As for the RunMojo/DebugMojo, how about moving deploy up the inheritance chain
into AbstractGwtShellMojo rather than duplicating it? (similar to the "gen"
option)
BTW, there are a bunch of options to DevMode that are missing in
RunMojo/DebugMojo: workDir, extra, etc. but I agree this one is a bit special,
as it defaults to outputing things that will end up in the artifact.
> add new gwt compiler option : -deploy
> -------------------------------------
>
> Key: MGWT-277
> URL: http://jira.codehaus.org/browse/MGWT-277
> Project: Maven 2.x GWT Plugin
> Issue Type: New Feature
> Affects Versions: 2.2.0
> Reporter: Olivier Lamy
> Assignee: nicolas de loof
> Fix For: 2.3.0-1
>
>
> option documentation :
> {code}
> -deploy The directory into which deployable but not servable output files
> will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar,
> and may be the same as the -extra directory/jar)
> {code}
--
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
