title: Can I force GWT compilation without entry point? (To validate compatibility to GWT)
body: <p>This question is related to, but not a duplicate of, <a href="https://stackoverflow.com/questions/1808197/how-do-i-compile-a-module-without-an-entrypoint">this question</a>.</p>
  
  <p>My issue is slightly different; I have a "utility module", shared between the client and server code, and it contains <em>no GWT-specific code</em>.</p>
  
  <p>I understand that normally, all the sources are pulled into one specific project, where everything is compiled together. But there is one issue with that: <em>I only get to know if my utility project is "GWT compatible", when I compile the main project</em>. This is way too late; I haven't even got around to start on the main project, but I want to know before I make a "commit" to my SCM, that my utility project is "GWT compatible".</p>
  
  <p>In other words, I want to validate the utility project for GWT compatibility, <em>independently from it's use in a separate project (module)</em>.</p>
  
  <p>There's a large part of the JRE that is not covered by GWT, and it is particularly likely in a utility module that non-GWT-compatible classes or method be used. That is what I want to validate against.</p>
  
  <p>EDIT: I <em>could</em> add a "dummy entry point", I suppose, but that makes the project depend on GWT, which I don't want to, since it is "general" code, also to be used by people that don't use GWT. If it matters, I use Maven as build system.</p>
  
  <p>EDIT2: No matter what I do, I will only get real compilation/validation with an entry point (does NOT need to reference any of the classes). Neither &lt;force&gt;true&lt;/force&gt;, nor &lt;failOnError&gt;true&lt;/failOnError&gt; will do. Is there a way I can define that entry point, for the <em>shared project</em>, such that only gwt-maven-plugin sees it, but not javac (so as not to add an unneeded dependency in the Java code)?</p>