Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In the answer below I'm assuming you're not using Maven. I tried to answer generically as well so the below should apply to any version control system (I'm on <a href="http://bazaar.canonical.com/en/">Bazaar</a>).</p> <p>You want to commit the files which constitute the application source code (e.g. *.java files) and configuration metadata (e.g. *.xml files). Some (like me) also like to commit Eclipse project configuration (.settings, .classpath and .project), even though doing so might on occasion cause some inconvenience to other team members due to differing Eclipse setups. I think the convenience of not needing to guess which Eclipse natures the project has or what's supposed to be on the classpath is worth it (<a href="http://maven.apache.org/">Maven</a> helps even more, but that's a separate discussion). </p> <p>You want to ignore the files and folders which are build products (and hence are temporary and reproducible by nature). For GWT apps developed in Eclipse using the <a href="http://code.google.com/eclipse/">Google Plugin for Eclipse</a> these are typically <code>war/WEB-INF/classes</code>, <code>war/WEB-INF/deploy</code> and <code>war/&lt;module_name&gt;</code>, where <code>&lt;module_name&gt;</code> is the name GWT uses for the folder where it places your GWT module compiled into JavaScript/HTML. You might also want to exclude <code>.gwt</code> where GWT dumps log information during work in Development Mode. </p> <p>Also in your project directory be sure to ignore the gwt-unitCache. This is where gwt stores a manifest of what units have been compiled for re-usability.</p> <p>Hope this helps.</p>
 

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