Note that there are some explanatory texts on larger screens.

plurals
  1. POIntelilJ 8.1 with 2 GWT modules
    primarykey
    data
    text
    <p>I'm trying to add the <a href="http://code.google.com/p/gwt-debug-panel/" rel="nofollow noreferrer">gwt-debugpanel</a> into my project. I'm using IntelliJ 8.1, and I've setup a stripped-down, bare-bones project for testing. The source tree looks like this:</p> <pre><code>gwt-multi-module src com.gindin dummy DummyApp.gwt.xml client DummyApp.java public DummyApp.css DummyApp.html debug DebugPanel.gwt.xml client GindinDebugPanel.java </code></pre> <p>Notes:</p> <ol> <li>All of the classes and files under the 'dummy' package were AutoGenerated by IntelliJ's "New -> GWT Module" wizard.</li> <li>The classes &amp; files under the 'debug' package were basically just copied over from the gwt-debugpanel's example project.</li> <li>I've added the necessary script &amp; reference to the nocache.js in the DummyApp.html</li> </ol> <p>Now, when I go to run the project in IntelliJ, the hosted shell gives me an error message:</p> <blockquote> <p>[TRACE] The development shell servlet received a request for 'com.gindin.debug.DebugPanel.nocache.js' in module 'com.gindin.dummy.DummyApp.gwt.xml' [WARN] Resource not found: com.gindin.debug.DebugPanel.nocache.js; (could a file be missing from the public path or a tag misconfigured in module com.gindin.dummy.DummyApp.gwt.xml ?)</p> </blockquote> <p>When I look at IntelliJ's module settings, the GWT facet shows both modules and their "Output Relative Paths".</p> <p>How do I get IntelliJ to do whatever it needs to do? Is there something I'm missing where I point IntelliJ at the 2nd module's entry point?</p> <p>thanks,</p> <p>jay</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload