SuperDevMode

[tbroyer]

SuperDevMode

[tbroyer]

See #1 and DevModeDesignDoc

BTW, gwt:generate-module runs in the generate-resources phase, which you should run (you should run up to and including process-classes) before running DevMode or SuperDevMode. gwt:generate-module generates the gwt.xml file in target/classes which should also be in your classpath for DevMode or SuperDevMode.

How are you running SuperDevMode? from your IDE? using the exec-maven-plugin? with which configuration? (classpath, arguments)

[h0ru5]

Got it working using exec-plugin, my first attempt was using eclipse run config.
I used this setup, confirmed orking for war, gwt-app and gwt-lib

<dependencies>  
    <dependency>
        <groupId>com.google.gwt</groupId>
        <artifactId>gwt-codeserver</artifactId>
        <version>2.6.0</version>
        <scope>test</scope>
    </dependency>
  </dependencies>
 <build>
        <plugins>
            <plugin>
                <groupId>net.ltgt.gwt.maven</groupId>
                <artifactId>gwt-maven-plugin</artifactId>
                <version>1.0-alpha-3</version>
                <extensions>true</extensions>
                <executions>
                    <execution>
                        <goals>
                            <goal>generate-module</goal>
                            <goal>compile</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <moduleName>${module.fullName}</moduleName>
                    <strict>true</strict>
                    <outputGen>true</outputGen>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>exec-maven-plugin</artifactId>
                <version>1.2.1</version>
                <configuration>
                    <classpathScope>test</classpathScope>
                    <mainClass>com.google.gwt.dev.codeserver.CodeServer</mainClass>
                    <arguments>
                        <argument>-src</argument>
                        <argument>src/main/java</argument>
                        <argument>${module.fullName}</argument>
                    </arguments>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>java</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
</build>

Of course a mojo would be nice, maybe with auto-injecting the prequesites into the .gwt.xml:

    <!-- SuperDev -->
    <add-linker name="xsiframe" />
    <set-configuration-property name="devModeRedirectEnabled" value="true" />
    <set-property name="compiler.useSourceMaps" value="true" />

[tbroyer]

Notes: devModeRedirectEnabled is on by default in GWT 2.6.0, xsiframe will be the default linker in the next release (and in 2.6 CodeServer automatically replaces the std linker with the xsiframe linker), and CodeServer automatically sets compiler.useSourceMaps. So none of these changes are necessary in the gwt.xml.

I'll try to hack something to launch the SuperDevMode (it's simpler than DevMode given that it doesn't serve the webapp / server-side code)

[h0ru5]

Thanks, Good to know!

Yes, I tried combining a forked jetty and codeserver for quick tests and debugging of client code, but its a much easier workflow IMHO to put the statics into public and use the codeserver alone .

[robert4os]

Hi,
I read that xsiframe and devModeRedirectEnabled would be the default, but I still find that both are needed to get super dev mode to work. What am I missing? Thanks!

https://code.google.com/p/google-web-toolkit/issues/detail?id=8681

[tbroyer]

gwt:codeserver was added in 1.0-beta-1