title: JAMES Mailet development process
body: <p>I'm starting a project that involves writing <a href="https://james.apache.org/server/head/mailet_api.html" rel="nofollow noreferrer">mailets</a> for <a href="http://james.apache.org/index.html" rel="nofollow noreferrer">Apache James</a>. As far as I can tell, the only way to test a change in my code (on Windows) is through the following steps:</p>
  
  <ol>
  <li>Compile the mailet code</li>
  <li>Build a jar file containing the mailet</li>
  <li>Copy the jar file into the <code>apps/james/SAR-INF/lib</code> directory</li>
  <li>Start JAMES from run.bat</li>
  <li>Run test</li>
  <li>Stop JAMES by telneting to port 4555 and issuing a shutdown command (I guess on Linux a SIGTERM would suffice)</li>
  </ol>
  
  <p>I can automate all these steps using Ant and some scripting magic, but I was wondering if I was missing something. Does anyone here have experience developing mailets? Did you use a similar process, or is there an easier way?</p>
  
  <p>For example, is there a way to make a running James instance reload the mailets JAR?</p>