title: Glassfish 4.x: using .reload mechanism in Eclipse?
body: <p>When I go to the Glassfish 4.x admin frontend and use the path to the unpackaged Eclipse build folder instead of uploading a WAR file, a simple "touch .reload" will trigger a relatively fast reload of the webapp container. However, when using the Eclipse plugin for Glassfish, the entire app gets packaged into a war and deployed after updating some class, which seems to be a really stupid thing to do during development.</p>
  
  <p>Is there any possibility to make the .reload mechanism work in Eclipse?</p>
  
  <p>From the command line, this can be done via</p>
  
  <pre><code>./asadmin redeploy --name jersey-war-example-1
  </code></pre>
  
  <p>which even eliminates the polling. Now I need to somehow turn this into an Eclipse build extension that does not start up a java instance just for that.</p>