$ mvn vaadin:help -Ddetail=true
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building vangkiem 1.0.0-BUILD-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- vaadin-maven-plugin:7.1.8:help (default-cli) @ vangkiem ---
[INFO] com.vaadin:vaadin-maven-plugin:7.1.8
Vaadin Plug-in for Maven
Maven plugin for Vaadin.
This plugin has 22 goals:
vaadin:browser
(no description available)
Available parameters:
browser (Default: C:Program FilesInternet Exploreriexplore.exe)
Path to the browser executable.
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
server (Default: ie)
Name of the BrowserManagerServer to lauch (typically, ie8)
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
vaadin:clean
Cleanup the webapp directory for GWT module compilation output
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:compile
Invokes the GWTCompiler for the project source. See compiler options :
http://code.google.com/intl/fr-FR/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions
Available parameters:
compileReport (Default: false)
add -compileReport parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.compileReport=true.
Expression: ${gwt.compiler.compileReport}
compilerMetrics (Default: false)
EXPERIMENTAL: add -XcompilerMetrics parameter to the compiler command line
Can be set from the command line using
-Dgwt.compiler.compilerMetrics=true
Expression: ${gwt.compiler.compilerMetrics}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
disableAggressiveOptimization (Default: false)
EXPERIMENTAL: add -XdisableAggressiveOptimization parameter to the
compiler command line
Can be set from the command line using
-Dgwt.compiler.disableAggressiveOptimization=true
Expression: ${gwt.compiler.disableAggressiveOptimization}
disableCastChecking (Default: false)
EXPERIMENTAL: Disables run-time checking of cast operations.
Can be set from command line using -Dgwt.disableCastChecking=true.
Expression: ${gwt.disableCastChecking}
disableClassMetadata (Default: false)
EXPERIMENTAL: Disables some java.lang.Class methods (e.g. getName()).
Can be set from command line using -Dgwt.disableClassMetadata=true.
Expression: ${gwt.disableClassMetadata}
disableRunAsync (Default: false)
EXPERIMENTAL: Disables code-splitting.
Can be set from command line using -Dgwt.disableRunAsync=true.
Expression: ${gwt.disableRunAsync}
draftCompile (Default: false)
Enable faster, but less-optimized, compilations.
Can be set from command line using -Dgwt.draftCompile=true.
This is equivalent to -Dgwt.compiler.optimizationLevel=0
-Dgwt.compiler.disableAggressiveOptimization=true.
Expression: ${gwt.draftCompile}
enableAssertions (Default: false)
Whether or not to enable assertions in generated scripts (-ea).
enableClosureCompiler (Default: false)
EXPERIMENTAL: add -XenableClosureCompiler parameter to the compiler
command line
Can be set from the command line using
-Dgwt.compiler.enableClosureCompiler=true
Expression: ${gwt.compiler.enableClosureCompiler}
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
extraParam (Default: false)
add -extra parameter to the compiler command line
Can be set from command line using -Dgwt.extraParam=true.
Expression: ${gwt.extraParam}
force (Default: false)
Dont try to detect if GWT compilation is up-to-date and can be skipped.
Can be set from command line using -Dgwt.compiler.force=true.
Expression: ${gwt.compiler.force}
fragmentCount (Default: -1)
EXPERIMENTAL: add -XfragmentCount parameter to the compiler command line
Can be set from the command line using -Dgwt.compiler.fragmentCount=n
Expression: ${gwt.compiler.fragmentCount}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
localWorkers
On GWT 1.6+, number of parallel processes used to compile GWT
premutations. Defaults to platform available processors number.
Can be unset from command line using -Dgwt.compiler.localWorkers=n.
Expression: ${gwt.compiler.localWorkers}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
optimizationLevel (Default: -1)
add -optimize parameter to the compiler command line the value must be
between 0 and 9 by default -1 so no arg to the compiler
Can be set from command line using -Dgwt.compiler.optimizationLevel=n.
Expression: ${gwt.compiler.optimizationLevel}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
skip (Default: false)
(no description available)
Expression: ${gwt.compiler.skip}
soycDetailed (Default: false)
add -XsoycDetailed parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.soycDetailed=true.
Expression: ${gwt.compiler.soycDetailed}
strict (Default: false)
add -strict parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.strict=true.
Expression: ${gwt.compiler.strict}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
treeLogger (Default: false)
Logs output in a graphical tree view.
Can be set from command line using -Dgwt.treeLogger=true.
Expression: ${gwt.treeLogger}
validateOnly (Default: false)
Validate all source code, but do not compile.
Can be set from command line using -Dgwt.validateOnly=true.
Expression: ${gwt.validateOnly}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
workDir
The temp directory is used for temporary compiled files (defaults is
system temp directory).
vaadin:compile-report
see
http://code.google.com/webtoolkit/doc/latest/DevGuideCompileReport.html#Usage
Available parameters:
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
outputDirectory (Default: ${project.reporting.outputDirectory})
The output directory for the report. Note that this parameter is only
evaluated if the goal is run directly from the command line. If the goal
is run indirectly as part of a site generation, the output directory
configured in the Maven Site Plugin is used instead.
Required: Yes
skip (Default: false)
(no description available)
Expression: ${gwt.compilerReport.skip}
vaadin:compile-theme
Updates Vaadin themes based on addons containing themes on the classpath.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
theme
A single theme. Option to specify a single module from command line
Expression: ${vaadin.theme}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:css
Creates CSS interfaces for css files. Will use the utility tool provided in
gwt sdk which create a corresponding Java interface for accessing the
classnames used in the file.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
cssFile
Shortcut for a single cssFile
cssFiles
List of resourceBundles that should be used to generate CSS interfaces.
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:debug
Extends the gwt goal and runs the project in the GWT Hosted mode with a
debugger port hook (optionally suspended).
Available parameters:
appEngineArtifactId (Default: appengine-java-sdk)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineArtifactId}
appEngineGroupId (Default: com.google.appengine)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineGroupId}
appEngineHome (Default: ${project.build.directory}/appengine-sdk/)
Location to find appengine sdk or to unzip downloaded one see
appEngineVersion
Expression: ${gwt.appEngineHome}
appEngineVersion (Default: 1.3.8)
set the appengine sdk to use
Artifact will be downloaded with groupId : appEngineGroupId and artifactId
appEngineArtifactId
Expression: ${gwt.appEngineVersion}
attachDebugger (Default: false)
Attach to the debugger application at the specified debugPort.
Expression: ${attachDebugger}
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
contextXml
Source Tomcat context.xml for GWT shell - copied to
/gwt/localhost/ROOT.xml (used as the context.xml for the SHELL - requires
Tomcat 5.0.x format - hence no default).
copyWebapp (Default: false)
Copies the contents of warSourceDirectory to hostedWebapp.
Can be set from command line using -Dgwt.copyWebapp=...
Expression: ${gwt.copyWebapp}
debugPort (Default: 8000)
Port to listen for debugger connection on.
Expression: ${gwt.debugPort}
debugSuspend (Default: true)
Whether or not to suspend execution until a debugger connects.
Expression: ${gwt.debugSuspend}
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
executedProject
The MavenProject executed by the compile phase
Expression: ${executedProject}
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noServer (Default: false)
Prevents the embedded GWT Tomcat server from running (even if a port is
specified).
Can be set from command line using -Dgwt.noserver=...
Expression: ${gwt.noserver}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port (Default: 8888)
Runs the embedded GWT server on the specified port.
runClasspathExcludes
List of Pattern jars to exclude from the classPath when running dev mode
runTarget
URL that should be automatically opened in the GWT shell. For example
com.myapp.gwt.Module/Module.html.
When the host page is outside the module public folder (for example, at
webapp root), the module MUST be specified (using a single in
configuration or by setting -Dgwt.module=..) and the runTarget parameter
can only contain the host page URI.
When the GWT module host page is part of the module public folder, the
runTarget MAY define the full GWT module path
(com.myapp.gwt.Module/Module.html) that will be automatically converted
according to the rename-to directive into renamed/Module.html.
Required: Yes
Expression: ${runTarget}
runTimeOut
Forked process execution timeOut (in seconds). Primary used for
integration-testing.
server
Specifies a different embedded web server to run (must implement
ServletContainerLauncher)
Expression: ${gwt.server}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
systemProperties
List of System properties to pass when running the hosted mode.
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
tomcat (Default: ${project.build.directory}/tomcat)
Specify the location on the filesystem for the generated embedded Tomcat
directory.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:eclipse
Goal which creates Eclipse lauch configurations for GWT modules.
Available parameters:
additionalPageParameters
Additional parameters to append to the module URL. For example, gwt-log
users will set log_level=DEBUG
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noserver (Default: false)
Run without hosted mode server
Expression: ${gwt.noserver}
port (Default: 8080)
Port of the HTTP server used when noserver is set
Expression: ${gwt.port}
useGoogleEclipsePlugin (Default: true)
Setup a launch configuration for using the Google Eclipse Plugin. This is
the recommended setup, as the home-made launch configuration has many
limitations. This parameter is only for backward compatibility, the
standard lauch configuration template will be removed in a future release.
Expression: ${use.google.eclipse.plugin}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:eclipseTest
Deprecated. use google eclipse plugin
http://code.google.com/intl/fr-FR/eclipse/docs/users_guide.html
Goal which creates Eclipse lauch configurations for GWTTestCases.
Available parameters:
batch
Configure batch execution of tests.
Value must be one of none, class or module.
Expression: ${gwt.test.batch}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
excludes
Comma separated list of ant-style exclusion patterns for GWT integration
tests
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
htmlunit (Default: FF3)
Configure options to run tests with HTMLUnit. The value must descrivbe the
browser emulation to be used, FF2, FF3, IE6, IE7, or IE8 (possible
multiple values separated by comas).
Expression: ${gwt.test.htmlunit}
includes (Default: **/GwtTest*.java,**/Gwt*Suite.java)
Comma separated list of ant-style inclusion patterns for GWT integration
tests. For example, can be set to **/*GwtTest.java to match all test
class following this naming convention. Surefire plugin may then ne
configured to exclude such tests.
It is recommended to use a TestSuite to run GwtTests, as they require some
huge setup and are very slow. Running inside a suite allow to execute the
setup only once. The default value is defined with this best practice in
mind.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mode (Default: manual)
Configure test mode. Can be set to manual, htmlunit, selenium or
remoteweb.
Expression: ${gwt.test.mode}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
out (Default: target/www-test)
output directory for code generated by GWT for tests
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
productionMode (Default: false)
run tests using production mode rather than development (a.k.a. hosted)
mode.
Expression: ${gwt.test.prod}
quirksMode (Default: false)
Run each test using an HTML document in quirks mode (rather than standards
mode)
remoteweb
Configure options to run tests RemoteWebBrowser. The value must describe
remote web URL, like rmi://myhost/ie8
You must start BrowserManagerServer before running tests with this option
(gwt:browser).
Expression: ${gwt.test.remoteweb}
reportsDirectory (Default: ${project.build.directory}/surefire-reports)
Directory for test reports, defaults to surefire one to match the
surefire-report plugin
selenium
Configure options to run tests with Selenium. The value must describe the
Selenium Remote Control target
Expression: ${gwt.test.selenium}
skip
Set this to true to bypass unit tests entirely. Its use is NOT
RECOMMENDED, especially if you enable it using the maven.test.skip
property, because maven.test.skip disables both running the tests and
compiling the tests. Consider using the skipTests parameter instead.
Expression: ${maven.test.skip}
skipExec
DEPRECATED This old parameter is just like skipTests, but bound to the old
property maven.test.skip.exec. Use -DskipTests instead; its shorter.
Expression: ${maven.test.skip.exec}
skipTests
Set this to true to skip running tests, but still compile them. Its use
is NOT RECOMMENDED, but quite convenient on occasion.
Expression: ${skipTests}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
testFailureIgnore
Set this to true to ignore a failure during testing. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
Expression: ${maven.test.failure.ignore}
testOutputDirectory (Default: ${project.build.directory}/www-test)
Location of the file.
testTimeOut (Default: 60)
Time out (in seconds) for test execution in dedicated JVM
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
userAgents
Specify the user agents to reduce the number of permutations in -prod
mode; e.g. ie6,ie8,safari,gecko1_8,opera
Expression: ${gwt.test.userAgents}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webMode (Default: false)
run tests using web mode rather than developer (a.k.a. hosted) mode
Expression: ${gwt.test.web}
vaadin:generateAsync
Goal which generate Asyn interface.
Available parameters:
encoding
(no description available)
Expression: ${project.build.sourceEncoding}
failOnError (Default: true)
Stop the build on error
Expression: ${maven.gwt.failOnError}
force (Default: false)
Pattern for GWT service interface
Expression: ${generateAsync.force}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
returnRequest (Default: false)
Return a com.google.gwt.http.client.Request on async interface to allow
cancellation.
rpcPattern (Default: {0})
A (MessageFormat) Pattern to get the GWT-RPC servlet URL based on service
interface name. For example to {0}.rpc if you want to map GWT-RPC calls
to *.rpc in web.xml, for example when using Spring dispatch servlet to
handle RPC requests.
Expression: ${gwt.rpcPattern}
servicePattern (Default: **/*Service.java)
Pattern for GWT service interface
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:help
Display help information on vaadin-maven-plugin.
Call
mvn vaadin:help -Ddetail=true -Dgoal=
to display parameter details.
Available parameters:
detail (Default: false)
If true, display all settable properties for each goal.
Expression: ${detail}
goal
The name of the goal for which to show help. If unspecified, all goals
will be displayed.
Expression: ${goal}
indentSize (Default: 2)
The number of spaces per indentation level, should be positive.
Expression: ${indentSize}
lineLength (Default: 80)
The maximum length of a display line, should be positive.
Expression: ${lineLength}
vaadin:i18n
Creates I18N interfaces for constants and messages files.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
i18nConstantsBundle
Shortcut for a single i18nConstantsBundle
i18nConstantsBundles
List of resourceBundles that should be used to generate i18n Constants
interfaces.
i18nConstantsWithLookupBundle
Shortcut for a single i18nConstantsWithLookupBundle
i18nConstantsWithLookupBundles
List of resourceBundles that should be used to generate i18n
ConstantsWithLookup interfaces.
i18nMessagesBundle
Shortcut for a single i18nMessagesBundle
i18nMessagesBundles
List of resourceBundles that should be used to generate i18n Messages
interfaces.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:mergewebxml
Merges GWT servlet elements into deployment descriptor (and non GWT servlets
into shell).
If you use scanRemoteServiceRelativePathAnnotation you must bind this mojo to
at least compile phase Because the classpath scanner need to see compile
classes
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mergedWebXml (Default: ${project.build.directory}/web.xml)
Location on filesystem where merged web.xml will be created. The
maven-war-plugin must be configured to use this path as webXml parameter
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
packageNamePerModule
(no description available)
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
scanRemoteServiceRelativePathAnnotation (Default: false)
(no description available)
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
vaadin:resources
Copy GWT java source code and module descriptor as resources in the build
outputDirectory. Alternative to declaring a in the POM with finer
filtering as the module descriptor is read to detect sources to be copied.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:run
Goal which run a GWT module in the GWT Hosted mode.
Available parameters:
appEngineArtifactId (Default: appengine-java-sdk)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineArtifactId}
appEngineGroupId (Default: com.google.appengine)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineGroupId}
appEngineHome (Default: ${project.build.directory}/appengine-sdk/)
Location to find appengine sdk or to unzip downloaded one see
appEngineVersion
Expression: ${gwt.appEngineHome}
appEngineVersion (Default: 1.3.8)
set the appengine sdk to use
Artifact will be downloaded with groupId : appEngineGroupId and artifactId
appEngineArtifactId
Expression: ${gwt.appEngineVersion}
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
contextXml
Source Tomcat context.xml for GWT shell - copied to
/gwt/localhost/ROOT.xml (used as the context.xml for the SHELL - requires
Tomcat 5.0.x format - hence no default).
copyWebapp (Default: false)
Copies the contents of warSourceDirectory to hostedWebapp.
Can be set from command line using -Dgwt.copyWebapp=...
Expression: ${gwt.copyWebapp}
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
executedProject
The MavenProject executed by the compile phase
Expression: ${executedProject}
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noServer (Default: false)
Prevents the embedded GWT Tomcat server from running (even if a port is
specified).
Can be set from command line using -Dgwt.noserver=...
Expression: ${gwt.noserver}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port (Default: 8888)
Runs the embedded GWT server on the specified port.
runClasspathExcludes
List of Pattern jars to exclude from the classPath when running dev mode
runTarget
URL that should be automatically opened in the GWT shell. For example
com.myapp.gwt.Module/Module.html.
When the host page is outside the module public folder (for example, at
webapp root), the module MUST be specified (using a single in
configuration or by setting -Dgwt.module=..) and the runTarget parameter
can only contain the host page URI.
When the GWT module host page is part of the module public folder, the
runTarget MAY define the full GWT module path
(com.myapp.gwt.Module/Module.html) that will be automatically converted
according to the rename-to directive into renamed/Module.html.
Required: Yes
Expression: ${runTarget}
runTimeOut
Forked process execution timeOut (in seconds). Primary used for
integration-testing.
server
Specifies a different embedded web server to run (must implement
ServletContainerLauncher)
Expression: ${gwt.server}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
systemProperties
List of System properties to pass when running the hosted mode.
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
tomcat (Default: ${project.build.directory}/tomcat)
Specify the location on the filesystem for the generated embedded Tomcat
directory.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:run-codeserver
EXPERIMENTAL: Runs GWT modules with Super Dev Mode.
Available parameters:
bindAddress
Set SuperDevModes bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
codeServerWorkDir
The root of the directory tree where the code server will write compiler
output. If not supplied, a temporary directory will be used.
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port
The port where the code server will run.
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:sdkInstall
Install a GWT (home built) SDK in local repository
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:source-jar
Add GWT java source code and module descriptor as resources to project jar.
Alternative to gwt:resources for better Eclipse projects synchronization.
Available parameters:
archive
The archive configuration to use. See Maven Archiver Reference.
finalName (Default: ${project.build.finalName})
Name of the generated JAR.
Required: Yes
Expression: ${jar.finalName}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:soyc
Deprecated. You must now use the CompileReport, SoycDashboard is not anymore
supported will be removed in 2.1.2
(no description available)
Available parameters:
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
outputDirectory (Default: ${project.reporting.outputDirectory})
The output directory for the report. Note that this parameter is only
evaluated if the goal is run directly from the command line. If the goal
is run indirectly as part of a site generation, the output directory
configured in the Maven Site Plugin is used instead.
Required: Yes
skip (Default: false)
(no description available)
Expression: ${gwt.soycReport.skip}
vaadin:test
Mimic surefire to run GWTTestCases during integration-test phase, until
SUREFIRE-508 is fixed
Available parameters:
batch
Configure batch execution of tests.
Value must be one of none, class or module.
Expression: ${gwt.test.batch}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
excludes
Comma separated list of ant-style exclusion patterns for GWT integration
tests
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
htmlunit (Default: FF3)
Configure options to run tests with HTMLUnit. The value must descrivbe the
browser emulation to be used, FF2, FF3, IE6, IE7, or IE8 (possible
multiple values separated by comas).
Expression: ${gwt.test.htmlunit}
includes (Default: **/GwtTest*.java,**/Gwt*Suite.java)
Comma separated list of ant-style inclusion patterns for GWT integration
tests. For example, can be set to **/*GwtTest.java to match all test
class following this naming convention. Surefire plugin may then ne
configured to exclude such tests.
It is recommended to use a TestSuite to run GwtTests, as they require some
huge setup and are very slow. Running inside a suite allow to execute the
setup only once. The default value is defined with this best practice in
mind.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mode (Default: manual)
Configure test mode. Can be set to manual, htmlunit, selenium or
remoteweb.
Expression: ${gwt.test.mode}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
out (Default: target/www-test)
output directory for code generated by GWT for tests
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
productionMode (Default: false)
run tests using production mode rather than development (a.k.a. hosted)
mode.
Expression: ${gwt.test.prod}
quirksMode (Default: false)
Run each test using an HTML document in quirks mode (rather than standards
mode)
remoteweb
Configure options to run tests RemoteWebBrowser. The value must describe
remote web URL, like rmi://myhost/ie8
You must start BrowserManagerServer before running tests with this option
(gwt:browser).
Expression: ${gwt.test.remoteweb}
reportsDirectory (Default: ${project.build.directory}/surefire-reports)
Directory for test reports, defaults to surefire one to match the
surefire-report plugin
selenium
Configure options to run tests with Selenium. The value must describe the
Selenium Remote Control target
Expression: ${gwt.test.selenium}
skip
Set this to true to bypass unit tests entirely. Its use is NOT
RECOMMENDED, especially if you enable it using the maven.test.skip
property, because maven.test.skip disables both running the tests and
compiling the tests. Consider using the skipTests parameter instead.
Expression: ${maven.test.skip}
skipExec
DEPRECATED This old parameter is just like skipTests, but bound to the old
property maven.test.skip.exec. Use -DskipTests instead; its shorter.
Expression: ${maven.test.skip.exec}
skipTests
Set this to true to skip running tests, but still compile them. Its use
is NOT RECOMMENDED, but quite convenient on occasion.
Expression: ${skipTests}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
testFailureIgnore
Set this to true to ignore a failure during testing. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
Expression: ${maven.test.failure.ignore}
testTimeOut (Default: 60)
Time out (in seconds) for test execution in dedicated JVM
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
userAgents
Specify the user agents to reduce the number of permutations in -prod
mode; e.g. ie6,ie8,safari,gecko1_8,opera
Expression: ${gwt.test.userAgents}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webMode (Default: false)
run tests using web mode rather than developer (a.k.a. hosted) mode
Expression: ${gwt.test.web}
vaadin:update-theme
Updates Vaadin themes based on addons containing themes on the classpath. This
goal is linked to phase generate-sources to make sure it is executed before
compile-theme.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
theme
A single theme. Option to specify a single module from command line
Expression: ${vaadin.theme}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:update-widgetset
Updates Vaadin widgetsets based on other widgetset packages on the classpath.
It is assumed that the project does not directly contain other GWT modules. In
part adapted from gwt-maven-plugin CompileMojo.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for or option to specify a single
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.727s
[INFO] Finished at: Tue Nov 26 14:29:57 MST 2013
[INFO] Final Memory: 6M/265M
[INFO] ------------------------------------------------------------------------
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building vangkiem 1.0.0-BUILD-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- vaadin-maven-plugin:7.1.8:help (default-cli) @ vangkiem ---
[INFO] com.vaadin:vaadin-maven-plugin:7.1.8
Vaadin Plug-in for Maven
Maven plugin for Vaadin.
This plugin has 22 goals:
vaadin:browser
(no description available)
Available parameters:
browser (Default: C:Program FilesInternet Exploreriexplore.exe)
Path to the browser executable.
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
server (Default: ie)
Name of the BrowserManagerServer to lauch (typically, ie8)
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
vaadin:clean
Cleanup the webapp directory for GWT module compilation output
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:compile
Invokes the GWTCompiler for the project source. See compiler options :
http://code.google.com/intl/fr-FR/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions
Available parameters:
compileReport (Default: false)
add -compileReport parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.compileReport=true.
Expression: ${gwt.compiler.compileReport}
compilerMetrics (Default: false)
EXPERIMENTAL: add -XcompilerMetrics parameter to the compiler command line
Can be set from the command line using
-Dgwt.compiler.compilerMetrics=true
Expression: ${gwt.compiler.compilerMetrics}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
disableAggressiveOptimization (Default: false)
EXPERIMENTAL: add -XdisableAggressiveOptimization parameter to the
compiler command line
Can be set from the command line using
-Dgwt.compiler.disableAggressiveOptimization=true
Expression: ${gwt.compiler.disableAggressiveOptimization}
disableCastChecking (Default: false)
EXPERIMENTAL: Disables run-time checking of cast operations.
Can be set from command line using -Dgwt.disableCastChecking=true.
Expression: ${gwt.disableCastChecking}
disableClassMetadata (Default: false)
EXPERIMENTAL: Disables some java.lang.Class methods (e.g. getName()).
Can be set from command line using -Dgwt.disableClassMetadata=true.
Expression: ${gwt.disableClassMetadata}
disableRunAsync (Default: false)
EXPERIMENTAL: Disables code-splitting.
Can be set from command line using -Dgwt.disableRunAsync=true.
Expression: ${gwt.disableRunAsync}
draftCompile (Default: false)
Enable faster, but less-optimized, compilations.
Can be set from command line using -Dgwt.draftCompile=true.
This is equivalent to -Dgwt.compiler.optimizationLevel=0
-Dgwt.compiler.disableAggressiveOptimization=true.
Expression: ${gwt.draftCompile}
enableAssertions (Default: false)
Whether or not to enable assertions in generated scripts (-ea).
enableClosureCompiler (Default: false)
EXPERIMENTAL: add -XenableClosureCompiler parameter to the compiler
command line
Can be set from the command line using
-Dgwt.compiler.enableClosureCompiler=true
Expression: ${gwt.compiler.enableClosureCompiler}
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
extraParam (Default: false)
add -extra parameter to the compiler command line
Can be set from command line using -Dgwt.extraParam=true.
Expression: ${gwt.extraParam}
force (Default: false)
Dont try to detect if GWT compilation is up-to-date and can be skipped.
Can be set from command line using -Dgwt.compiler.force=true.
Expression: ${gwt.compiler.force}
fragmentCount (Default: -1)
EXPERIMENTAL: add -XfragmentCount parameter to the compiler command line
Can be set from the command line using -Dgwt.compiler.fragmentCount=n
Expression: ${gwt.compiler.fragmentCount}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
localWorkers
On GWT 1.6+, number of parallel processes used to compile GWT
premutations. Defaults to platform available processors number.
Can be unset from command line using -Dgwt.compiler.localWorkers=n.
Expression: ${gwt.compiler.localWorkers}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
optimizationLevel (Default: -1)
add -optimize parameter to the compiler command line the value must be
between 0 and 9 by default -1 so no arg to the compiler
Can be set from command line using -Dgwt.compiler.optimizationLevel=n.
Expression: ${gwt.compiler.optimizationLevel}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
skip (Default: false)
(no description available)
Expression: ${gwt.compiler.skip}
soycDetailed (Default: false)
add -XsoycDetailed parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.soycDetailed=true.
Expression: ${gwt.compiler.soycDetailed}
strict (Default: false)
add -strict parameter to the compiler command line
Can be set from command line using -Dgwt.compiler.strict=true.
Expression: ${gwt.compiler.strict}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
treeLogger (Default: false)
Logs output in a graphical tree view.
Can be set from command line using -Dgwt.treeLogger=true.
Expression: ${gwt.treeLogger}
validateOnly (Default: false)
Validate all source code, but do not compile.
Can be set from command line using -Dgwt.validateOnly=true.
Expression: ${gwt.validateOnly}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
workDir
The temp directory is used for temporary compiled files (defaults is
system temp directory).
vaadin:compile-report
see
http://code.google.com/webtoolkit/doc/latest/DevGuideCompileReport.html#Usage
Available parameters:
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
outputDirectory (Default: ${project.reporting.outputDirectory})
The output directory for the report. Note that this parameter is only
evaluated if the goal is run directly from the command line. If the goal
is run indirectly as part of a site generation, the output directory
configured in the Maven Site Plugin is used instead.
Required: Yes
skip (Default: false)
(no description available)
Expression: ${gwt.compilerReport.skip}
vaadin:compile-theme
Updates Vaadin themes based on addons containing themes on the classpath.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
theme
A single theme. Option to specify a single module from command line
Expression: ${vaadin.theme}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:css
Creates CSS interfaces for css files. Will use the utility tool provided in
gwt sdk which create a corresponding Java interface for accessing the
classnames used in the file.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
cssFile
Shortcut for a single cssFile
cssFiles
List of resourceBundles that should be used to generate CSS interfaces.
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:debug
Extends the gwt goal and runs the project in the GWT Hosted mode with a
debugger port hook (optionally suspended).
Available parameters:
appEngineArtifactId (Default: appengine-java-sdk)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineArtifactId}
appEngineGroupId (Default: com.google.appengine)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineGroupId}
appEngineHome (Default: ${project.build.directory}/appengine-sdk/)
Location to find appengine sdk or to unzip downloaded one see
appEngineVersion
Expression: ${gwt.appEngineHome}
appEngineVersion (Default: 1.3.8)
set the appengine sdk to use
Artifact will be downloaded with groupId : appEngineGroupId and artifactId
appEngineArtifactId
Expression: ${gwt.appEngineVersion}
attachDebugger (Default: false)
Attach to the debugger application at the specified debugPort.
Expression: ${attachDebugger}
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
contextXml
Source Tomcat context.xml for GWT shell - copied to
/gwt/localhost/ROOT.xml (used as the context.xml for the SHELL - requires
Tomcat 5.0.x format - hence no default).
copyWebapp (Default: false)
Copies the contents of warSourceDirectory to hostedWebapp.
Can be set from command line using -Dgwt.copyWebapp=...
Expression: ${gwt.copyWebapp}
debugPort (Default: 8000)
Port to listen for debugger connection on.
Expression: ${gwt.debugPort}
debugSuspend (Default: true)
Whether or not to suspend execution until a debugger connects.
Expression: ${gwt.debugSuspend}
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
executedProject
The MavenProject executed by the compile phase
Expression: ${executedProject}
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noServer (Default: false)
Prevents the embedded GWT Tomcat server from running (even if a port is
specified).
Can be set from command line using -Dgwt.noserver=...
Expression: ${gwt.noserver}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port (Default: 8888)
Runs the embedded GWT server on the specified port.
runClasspathExcludes
List of Pattern jars to exclude from the classPath when running dev mode
runTarget
URL that should be automatically opened in the GWT shell. For example
com.myapp.gwt.Module/Module.html.
When the host page is outside the module public folder (for example, at
webapp root), the module MUST be specified (using a single
configuration or by setting -Dgwt.module=..) and the runTarget parameter
can only contain the host page URI.
When the GWT module host page is part of the module public folder, the
runTarget MAY define the full GWT module path
(com.myapp.gwt.Module/Module.html) that will be automatically converted
according to the rename-to directive into renamed/Module.html.
Required: Yes
Expression: ${runTarget}
runTimeOut
Forked process execution timeOut (in seconds). Primary used for
integration-testing.
server
Specifies a different embedded web server to run (must implement
ServletContainerLauncher)
Expression: ${gwt.server}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
systemProperties
List of System properties to pass when running the hosted mode.
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
tomcat (Default: ${project.build.directory}/tomcat)
Specify the location on the filesystem for the generated embedded Tomcat
directory.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:eclipse
Goal which creates Eclipse lauch configurations for GWT modules.
Available parameters:
additionalPageParameters
Additional parameters to append to the module URL. For example, gwt-log
users will set log_level=DEBUG
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noserver (Default: false)
Run without hosted mode server
Expression: ${gwt.noserver}
port (Default: 8080)
Port of the HTTP server used when noserver is set
Expression: ${gwt.port}
useGoogleEclipsePlugin (Default: true)
Setup a launch configuration for using the Google Eclipse Plugin. This is
the recommended setup, as the home-made launch configuration has many
limitations. This parameter is only for backward compatibility, the
standard lauch configuration template will be removed in a future release.
Expression: ${use.google.eclipse.plugin}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:eclipseTest
Deprecated. use google eclipse plugin
http://code.google.com/intl/fr-FR/eclipse/docs/users_guide.html
Goal which creates Eclipse lauch configurations for GWTTestCases.
Available parameters:
batch
Configure batch execution of tests.
Value must be one of none, class or module.
Expression: ${gwt.test.batch}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
excludes
Comma separated list of ant-style exclusion patterns for GWT integration
tests
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
htmlunit (Default: FF3)
Configure options to run tests with HTMLUnit. The value must descrivbe the
browser emulation to be used, FF2, FF3, IE6, IE7, or IE8 (possible
multiple values separated by comas).
Expression: ${gwt.test.htmlunit}
includes (Default: **/GwtTest*.java,**/Gwt*Suite.java)
Comma separated list of ant-style inclusion patterns for GWT integration
tests. For example, can be set to **/*GwtTest.java to match all test
class following this naming convention. Surefire plugin may then ne
configured to exclude such tests.
It is recommended to use a TestSuite to run GwtTests, as they require some
huge setup and are very slow. Running inside a suite allow to execute the
setup only once. The default value is defined with this best practice in
mind.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mode (Default: manual)
Configure test mode. Can be set to manual, htmlunit, selenium or
remoteweb.
Expression: ${gwt.test.mode}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
out (Default: target/www-test)
output directory for code generated by GWT for tests
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
productionMode (Default: false)
run tests using production mode rather than development (a.k.a. hosted)
mode.
Expression: ${gwt.test.prod}
quirksMode (Default: false)
Run each test using an HTML document in quirks mode (rather than standards
mode)
remoteweb
Configure options to run tests RemoteWebBrowser. The value must describe
remote web URL, like rmi://myhost/ie8
You must start BrowserManagerServer before running tests with this option
(gwt:browser).
Expression: ${gwt.test.remoteweb}
reportsDirectory (Default: ${project.build.directory}/surefire-reports)
Directory for test reports, defaults to surefire one to match the
surefire-report plugin
selenium
Configure options to run tests with Selenium. The value must describe the
Selenium Remote Control target
Expression: ${gwt.test.selenium}
skip
Set this to true to bypass unit tests entirely. Its use is NOT
RECOMMENDED, especially if you enable it using the maven.test.skip
property, because maven.test.skip disables both running the tests and
compiling the tests. Consider using the skipTests parameter instead.
Expression: ${maven.test.skip}
skipExec
DEPRECATED This old parameter is just like skipTests, but bound to the old
property maven.test.skip.exec. Use -DskipTests instead; its shorter.
Expression: ${maven.test.skip.exec}
skipTests
Set this to true to skip running tests, but still compile them. Its use
is NOT RECOMMENDED, but quite convenient on occasion.
Expression: ${skipTests}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
testFailureIgnore
Set this to true to ignore a failure during testing. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
Expression: ${maven.test.failure.ignore}
testOutputDirectory (Default: ${project.build.directory}/www-test)
Location of the file.
testTimeOut (Default: 60)
Time out (in seconds) for test execution in dedicated JVM
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
userAgents
Specify the user agents to reduce the number of permutations in -prod
mode; e.g. ie6,ie8,safari,gecko1_8,opera
Expression: ${gwt.test.userAgents}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webMode (Default: false)
run tests using web mode rather than developer (a.k.a. hosted) mode
Expression: ${gwt.test.web}
vaadin:generateAsync
Goal which generate Asyn interface.
Available parameters:
encoding
(no description available)
Expression: ${project.build.sourceEncoding}
failOnError (Default: true)
Stop the build on error
Expression: ${maven.gwt.failOnError}
force (Default: false)
Pattern for GWT service interface
Expression: ${generateAsync.force}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
returnRequest (Default: false)
Return a com.google.gwt.http.client.Request on async interface to allow
cancellation.
rpcPattern (Default: {0})
A (MessageFormat) Pattern to get the GWT-RPC servlet URL based on service
interface name. For example to {0}.rpc if you want to map GWT-RPC calls
to *.rpc in web.xml, for example when using Spring dispatch servlet to
handle RPC requests.
Expression: ${gwt.rpcPattern}
servicePattern (Default: **/*Service.java)
Pattern for GWT service interface
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:help
Display help information on vaadin-maven-plugin.
Call
mvn vaadin:help -Ddetail=true -Dgoal=
to display parameter details.
Available parameters:
detail (Default: false)
If true, display all settable properties for each goal.
Expression: ${detail}
goal
The name of the goal for which to show help. If unspecified, all goals
will be displayed.
Expression: ${goal}
indentSize (Default: 2)
The number of spaces per indentation level, should be positive.
Expression: ${indentSize}
lineLength (Default: 80)
The maximum length of a display line, should be positive.
Expression: ${lineLength}
vaadin:i18n
Creates I18N interfaces for constants and messages files.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
i18nConstantsBundle
Shortcut for a single i18nConstantsBundle
i18nConstantsBundles
List of resourceBundles that should be used to generate i18n Constants
interfaces.
i18nConstantsWithLookupBundle
Shortcut for a single i18nConstantsWithLookupBundle
i18nConstantsWithLookupBundles
List of resourceBundles that should be used to generate i18n
ConstantsWithLookup interfaces.
i18nMessagesBundle
Shortcut for a single i18nMessagesBundle
i18nMessagesBundles
List of resourceBundles that should be used to generate i18n Messages
interfaces.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:mergewebxml
Merges GWT servlet elements into deployment descriptor (and non GWT servlets
into shell).
If you use scanRemoteServiceRelativePathAnnotation you must bind this mojo to
at least compile phase Because the classpath scanner need to see compile
classes
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mergedWebXml (Default: ${project.build.directory}/web.xml)
Location on filesystem where merged web.xml will be created. The
maven-war-plugin must be configured to use this path as webXml parameter
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
packageNamePerModule
(no description available)
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
scanRemoteServiceRelativePathAnnotation (Default: false)
(no description available)
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
vaadin:resources
Copy GWT java source code and module descriptor as resources in the build
outputDirectory. Alternative to declaring a
filtering as the module descriptor is read to detect sources to be copied.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:run
Goal which run a GWT module in the GWT Hosted mode.
Available parameters:
appEngineArtifactId (Default: appengine-java-sdk)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineArtifactId}
appEngineGroupId (Default: com.google.appengine)
groupId to download appengine sdk from maven repo
Expression: ${gwt.appEngineGroupId}
appEngineHome (Default: ${project.build.directory}/appengine-sdk/)
Location to find appengine sdk or to unzip downloaded one see
appEngineVersion
Expression: ${gwt.appEngineHome}
appEngineVersion (Default: 1.3.8)
set the appengine sdk to use
Artifact will be downloaded with groupId : appEngineGroupId and artifactId
appEngineArtifactId
Expression: ${gwt.appEngineVersion}
bindAddress
Set GWT shell bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
blacklist
Set GWT shell protocol/host blacklist.
Can be set from command line using -Dgwt.blacklist=...
Expression: ${gwt.blacklist}
buildOutputDirectory (Default: ${project.build.outputDirectory})
Location of the compiled classes.
Required: Yes
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
contextXml
Source Tomcat context.xml for GWT shell - copied to
/gwt/localhost/ROOT.xml (used as the context.xml for the SHELL - requires
Tomcat 5.0.x format - hence no default).
copyWebapp (Default: false)
Copies the contents of warSourceDirectory to hostedWebapp.
Can be set from command line using -Dgwt.copyWebapp=...
Expression: ${gwt.copyWebapp}
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
executedProject
The MavenProject executed by the compile phase
Expression: ${executedProject}
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
hostedWebapp (Default:
${project.build.directory}/${project.build.finalName})
Location of the hosted-mode web application structure.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
noServer (Default: false)
Prevents the embedded GWT Tomcat server from running (even if a port is
specified).
Can be set from command line using -Dgwt.noserver=...
Expression: ${gwt.noserver}
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port (Default: 8888)
Runs the embedded GWT server on the specified port.
runClasspathExcludes
List of Pattern jars to exclude from the classPath when running dev mode
runTarget
URL that should be automatically opened in the GWT shell. For example
com.myapp.gwt.Module/Module.html.
When the host page is outside the module public folder (for example, at
webapp root), the module MUST be specified (using a single
configuration or by setting -Dgwt.module=..) and the runTarget parameter
can only contain the host page URI.
When the GWT module host page is part of the module public folder, the
runTarget MAY define the full GWT module path
(com.myapp.gwt.Module/Module.html) that will be automatically converted
according to the rename-to directive into renamed/Module.html.
Required: Yes
Expression: ${runTarget}
runTimeOut
Forked process execution timeOut (in seconds). Primary used for
integration-testing.
server
Specifies a different embedded web server to run (must implement
ServletContainerLauncher)
Expression: ${gwt.server}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
systemProperties
List of System properties to pass when running the hosted mode.
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
tomcat (Default: ${project.build.directory}/tomcat)
Specify the location on the filesystem for the generated embedded Tomcat
directory.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webXml (Default: ${basedir}/src/main/webapp/WEB-INF/web.xml)
Source web.xml deployment descriptor that is used for GWT shell and for
deployment WAR to merge servlet entries.
Required: Yes
webXmlServletPathAsIs (Default: false)
Specifies whether or not to add the module name as a prefix to the servlet
path when merging web.xml. If you set this to false the exact path from
the GWT module will be used, nothing else will be prepended.
whitelist
Set GWT shell protocol/host whitelist.
Can be set from command line using -Dgwt.whitelist=...
Expression: ${gwt.whitelist}
vaadin:run-codeserver
EXPERIMENTAL: Runs GWT modules with Super Dev Mode.
Available parameters:
bindAddress
Set SuperDevModes bindAddress.
Can be set from command line using -Dgwt.bindAddress=...
Expression: ${gwt.bindAddress}
codeServerWorkDir
The root of the directory tree where the code server will write compiler
output. If not supplied, a temporary directory will be used.
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
port
The port where the code server will run.
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:sdkInstall
Install a GWT (home built) SDK in local repository
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:source-jar
Add GWT java source code and module descriptor as resources to project jar.
Alternative to gwt:resources for better Eclipse projects synchronization.
Available parameters:
archive
The archive configuration to use. See Maven Archiver Reference.
finalName (Default: ${project.build.finalName})
Name of the generated JAR.
Required: Yes
Expression: ${jar.finalName}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:soyc
Deprecated. You must now use the CompileReport, SoycDashboard is not anymore
supported will be removed in 2.1.2
(no description available)
Available parameters:
extra (Default: ${project.build.directory}/extra)
The directory into which extra, non-deployed files will be written.
outputDirectory (Default: ${project.reporting.outputDirectory})
The output directory for the report. Note that this parameter is only
evaluated if the goal is run directly from the command line. If the goal
is run indirectly as part of a site generation, the output directory
configured in the Maven Site Plugin is used instead.
Required: Yes
skip (Default: false)
(no description available)
Expression: ${gwt.soycReport.skip}
vaadin:test
Mimic surefire to run GWTTestCases during integration-test phase, until
SUREFIRE-508 is fixed
Available parameters:
batch
Configure batch execution of tests.
Value must be one of none, class or module.
Expression: ${gwt.test.batch}
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
excludes
Comma separated list of ant-style exclusion patterns for GWT integration
tests
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
htmlunit (Default: FF3)
Configure options to run tests with HTMLUnit. The value must descrivbe the
browser emulation to be used, FF2, FF3, IE6, IE7, or IE8 (possible
multiple values separated by comas).
Expression: ${gwt.test.htmlunit}
includes (Default: **/GwtTest*.java,**/Gwt*Suite.java)
Comma separated list of ant-style inclusion patterns for GWT integration
tests. For example, can be set to **/*GwtTest.java to match all test
class following this naming convention. Surefire plugin may then ne
configured to exclude such tests.
It is recommended to use a TestSuite to run GwtTests, as they require some
huge setup and are very slow. Running inside a suite allow to execute the
setup only once. The default value is defined with this best practice in
mind.
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
mode (Default: manual)
Configure test mode. Can be set to manual, htmlunit, selenium or
remoteweb.
Expression: ${gwt.test.mode}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
out (Default: target/www-test)
output directory for code generated by GWT for tests
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
productionMode (Default: false)
run tests using production mode rather than development (a.k.a. hosted)
mode.
Expression: ${gwt.test.prod}
quirksMode (Default: false)
Run each test using an HTML document in quirks mode (rather than standards
mode)
remoteweb
Configure options to run tests RemoteWebBrowser. The value must describe
remote web URL, like rmi://myhost/ie8
You must start BrowserManagerServer before running tests with this option
(gwt:browser).
Expression: ${gwt.test.remoteweb}
reportsDirectory (Default: ${project.build.directory}/surefire-reports)
Directory for test reports, defaults to surefire one to match the
surefire-report plugin
selenium
Configure options to run tests with Selenium. The value must describe the
Selenium Remote Control target
Expression: ${gwt.test.selenium}
skip
Set this to true to bypass unit tests entirely. Its use is NOT
RECOMMENDED, especially if you enable it using the maven.test.skip
property, because maven.test.skip disables both running the tests and
compiling the tests. Consider using the skipTests parameter instead.
Expression: ${maven.test.skip}
skipExec
DEPRECATED This old parameter is just like skipTests, but bound to the old
property maven.test.skip.exec. Use -DskipTests instead; its shorter.
Expression: ${maven.test.skip.exec}
skipTests
Set this to true to skip running tests, but still compile them. Its use
is NOT RECOMMENDED, but quite convenient on occasion.
Expression: ${skipTests}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
testFailureIgnore
Set this to true to ignore a failure during testing. Its use is NOT
RECOMMENDED, but quite convenient on occasion.
Expression: ${maven.test.failure.ignore}
testTimeOut (Default: 60)
Time out (in seconds) for test execution in dedicated JVM
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
userAgents
Specify the user agents to reduce the number of permutations in -prod
mode; e.g. ie6,ie8,safari,gecko1_8,opera
Expression: ${gwt.test.userAgents}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
webMode (Default: false)
run tests using web mode rather than developer (a.k.a. hosted) mode
Expression: ${gwt.test.web}
vaadin:update-theme
Updates Vaadin themes based on addons containing themes on the classpath. This
goal is linked to phase generate-sources to make sure it is executed before
compile-theme.
Available parameters:
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
theme
A single theme. Option to specify a single module from command line
Expression: ${vaadin.theme}
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
vaadin:update-widgetset
Updates Vaadin widgetsets based on other widgetset packages on the classpath.
It is assumed that the project does not directly contain other GWT modules. In
part adapted from gwt-maven-plugin CompileMojo.
Available parameters:
compileSourcesArtifacts
Artifacts to be included as source-jars in GWTCompiler Classpath. Removes
the restriction that source code must be bundled inside of the final JAR
when dealing with external utility libraries not designed exclusivelly for
GWT. The plugin will download the source.jar if necessary. This option is
a workaround to avoid packaging sources inside the same JAR when splitting
and application into modules. A smaller JAR can then be used on server
classpath and distributed without sources (that may not be desirable).
deploy
The directory into which deployable but not servable output files will be
written (defaults to WEB-INF/deploy under the webappDirectory
directory/jar, and may be the same as the extra directory/jar)
extraJvmArgs (Default: -Xmx512m)
Extra JVM arguments that are passed to the GWT-Maven generated scripts
(for compiler, shell, etc - typically use -Xmx512m here, or
-XstartOnFirstThread, etc).
Can be set from command line using -Dgwt.extraJvmArgs=..., defaults to
setting max Heap size to be large enough for most GWT use cases.
Expression: ${gwt.extraJvmArgs}
gen (Default: ${project.build.directory}/.generated)
Location on filesystem where GWT will write generated content for review
(-gen option to GWT Compiler).
Can be set from command line using -Dgwt.gen=...
Expression: ${gwt.gen}
generateDirectory (Default:
${project.build.directory}/generated-sources/gwt)
Folder where generated-source will be created (automatically added to
compile classpath).
Required: Yes
genParam (Default: true)
Whether to add -gen parameter to the compiler command line
Can be set from command line using -Dgwt.genParam=false. Defaults to
true for backwards compatibility.
Expression: ${gwt.genParam}
gwtSdkFirstInClasspath (Default: false)
The forked command line will use gwt sdk jars first in classpath. see
issue http://code.google.com/p/google-web-toolkit/issues/detail?id=5290
Expression: ${gwt.gwtSdkFirstInClasspath}
inplace (Default: false)
Select the place where GWT application is built. In inplace mode, the
warSourceDirectory is used to match the same use case of the war:inplace
http://maven.apache.org/plugins/maven-war-plugin/inplace-mojo.html goal.
Expression: ${gwt.inplace}
jvm
Option to specify the jvm (or path to the java executable) to use with the
forking scripts. For the default, the jvm will be the same as the one used
to run Maven.
Expression: ${gwt.jvm}
logLevel (Default: INFO)
GWT logging level (-logLevel ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or
ALL).
Can be set from command line using -Dgwt.logLevel=...
Expression: ${gwt.logLevel}
module
A single GWT module. Shortcut for
module from command line
Expression: ${gwt.module}
modules
The project GWT modules. If not set, the plugin will scan the project for
.gwt.xml files.
persistentunitcache
Whether to use the persistent unit cache or not.
Can be set from command line using -Dgwt.persistentunitcache=...
Expression: ${gwt.persistentunitcache}
persistentunitcachedir
The directory where the persistent unit cache will be created if enabled.
Can be set from command line using -Dgwt.persistentunitcachedir=...
Expression: ${gwt.persistentunitcachedir}
style (Default: OBF)
GWT JavaScript compiler output style (-style OBF[USCATED], PRETTY, or
DETAILED).
Can be set from command line using -Dgwt.style=...
Expression: ${gwt.style}
timeOut
Forked process execution timeOut. Usefull to avoid maven to hang in
continuous integration server.
warSourceDirectory (Default: ${basedir}/src/main/webapp)
Location of the web application static resources (same as maven-war-plugin
parameter)
webappDirectory (Default:
${project.build.directory}/${project.build.finalName})
Location on filesystem where GWT will write output files (-out option to
GWTCompiler).
Expression: ${gwt.war}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.727s
[INFO] Finished at: Tue Nov 26 14:29:57 MST 2013
[INFO] Final Memory: 6M/265M
[INFO] ------------------------------------------------------------------------
0 komentar:
Posting Komentar