Re: How to configure Super Dev Mode in Eclipse ?

On Thursday, July 19, 2012 1:31:40 AM UTC+2, regnoult axel wrote:

Hello,

I am unsuccessfully configurating Super Dev Mode in Eclipse ( Eclipse Java EE IDE for Web Developers, Version: Indigo Service Release 2 )....

To be simple, I am just finding the easiest way (maybe it is easier without eclipse ?) to use/configure Super Dev Mode...I know the documentation explain "things", but I am more likely looking for a kind of tutorial for newbies.

If you're using Maven, try "mvn gwt:run-codeserver" with the 2.5.0-rc1 gwt-maven-plugin ;-)

(it won't work well with multi-module builds though, just like "mvn gwt:run")

 

First, I go to Run Configuration and then I have various questions/problems :

#1 - Should I create the new configuration for a Web Application or a Java Application ? (because in the following link, it is doing a Java Configuration : http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html) ?

#2 - I am asuming that I should use a configuration for a web application (like I had with the Normal Dev Mode). So then I do not why Eclipse is always adding the following  (even if I remove them and save the config) :

-remoteUI "${gwt_remote_ui_server_port}:${unique_id}" -logLevel INFO -codeServerPort 9997 -server com.google.appengine.tools.development.gwt.AppEngineLauncher -war C:\MS\workDir

Is it a bug ?

As "emurmur" said, you should choose "Java Application". "Web Application" is (for now at least) tailored for DevMode.

 

#3 - Configuring the JRE, I do not know if I should use the JDK6 or JDK7 ? If I use JDK6 Eclipse says (I have the same problem with normal dev mode. ) :
JRE not compatible with workspace .class file compatibility: 1.7

Which JDK should I use ?

It really doesn't matter.

You should however set the compatibility level to 1.6: GWT only deals with Java 6, so using 1.7 as the compatibility level could lead to Eclipse using Java 7 specific syntax/features. 1.6 would be safer.

 

#4 - Is there any mandatory argument to add (such as -workDir or [module]...) ? Because I put this application argument line :

-src C:\MS\src\com -workDir C:\MS\workDir -port auto com.mananaseguro.MananaSeguro

 I had many times the following error : Working directory does not exist: com.mananaseguro.MananaSeguro

This is strange.

If you wonder which options are available though, just throw some non-existing one (such as "-foo") and it'll fail listing the available options (I believe "-help" would work too)

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ZO_24u5yYr0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.