Jens, Below is the message I am getting. Not sure which one to use or how to use.
Unknown argument: -out Google Web Toolkit 2.7.0 DevMode [-[no]startServer] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort port-number | "auto"] [-[no]superDevMode] [-server servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] [-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s] where -[no]startServer Starts a servlet container serving the directory specified by the -war flag. (defaults to ON) -port Specifies the TCP port for the embedded web server (defaults to 8888) -whitelist Allows the user to browse URLs that match the specified regexes (comma or space separated) -blacklist Prevents the user browsing URLs that match the specified regexes (comma or space separated) -logdir Logs to a file in the given directory, as well as graphically -logLevel The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL -gen Debugging: causes normally-transient generated types to be saved in the specified directory -bindAddress Specifies the bind address for the code server and web server (defaults to 127.0.0.1) -codeServerPort Specifies the TCP port for the code server (defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode) -[no]superDevMode Runs Super Dev Mode instead of classic Development Mode. (defaults to ON) -server Specify a different embedded web server to run (must implement ServletContainerLauncher) -startupUrl Automatically launches the specified URL -war The directory into which deployable output files will be written (defaults to 'war') -deploy The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar) -extra The directory into which extra files, not intended for deployment, will be written -modulePathPrefix The subdirectory inside the war dir where DevMode will create module directories. (defaults empty for top level) -workDir The compiler's working directory for internal use (must be writeable; defaults to a system temp dir) -XmethodNameDisplayMode Emit extra information allow chrome dev tools to display Java identifiers in many places instead of JavaScript functions. -sourceLevel Specifies Java source level (defaults to auto:1.6) -XjsInteropMode Specifies JsInterop mode, either NONE, JS, or CLOSURE (defaults to NONE) -[no]incremental Compiles faster by reusing data from the previous compile. (defaults to ON) and module[s] Specifies the name(s) of the module(s) to host *Can you please help me in rewriting this line based on the above suggestions ?* *<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-out www mmsea/app.jsp -noserver -port 9080"/>* Thanks a lot. On Tuesday, February 24, 2015 at 10:39:30 AM UTC-5, Jens wrote: > > > Thanks Jens. I still have the 2nd error "Unknown argument: -out" >> > > The DevMode class should show you all valid arguments and the description > should tell you which one to choose as a replacement. I don't know anything > about GWT 1.7, but I assume DevMode -war is probably the same as GWTShell > -out. > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
