GWT SuperDev mode enabled, source maps enabled, co

2019-06-18 05:48发布

As the title says, I'm attempting to run SuperDev mode using the latest version of GWT (2.6.1) in Chrome.

My application is being served by a Tomcat server. I have the SuperDev mode server running (via IntelliJ), which compiles and links the sources successfully, and source maps are enabled in Chrome. I go to the application (http://localhost:8081/example/#example). When it loads, I compile using the DevMode On bookmark. When it's done compiling, I don't see any Java sources in the Chrome developer tools.

I also have the following properties set in my applications .gwt.xml

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

I'm not sure what else I'm missing? From the various resources I've found online, it appears I have all of my bases covered, so I'm not sure why the source maps won't show up.

1条回答
The star\"
2楼-- · 2019-06-18 06:26

The problem likely is that your .gwt.xml allows several permutations, but SuperDevMode cannot provide source map for several versions of code. Check the logs of SuperDevMode process - it should have corresponding message there.

So, just try to make your module in .gwt.xml produce only one permutation. If you use standard GWT libs only, it would be enough to place there

<set-property name="user.agent" value="safari" />

For GXT-driven project, use this one instead:

<set-property name="gxt.user.agent" value="chrome" />

For MGWT-driven project try to use these lines:

<set-property name="user.agent" value="safari"/>
<set-property name="mgwt.os" value="desktop" />

As a positive side-effect of having only one permutation will be the shortest re-compiling time for your project when you develop it ;)

Hope this helps.

查看更多
登录 后发表回答