<p>For the past 2 years-(ish) I've been using <a href="http://maven.apache.org" rel="nofollow noreferrer">Maven2</a> for my build/continuous integration solution.  I used <a href="http://ant.apache.org" rel="nofollow noreferrer">Ant</a> a bit before that but really didn't get a lot of experience with it.  Now I've taken a new job and the team I'm on now uses Ant.  </p>

<p>What I'm wondering about is this:</p>

<p>In Maven we had directory conventions for seperating our java source and files and java test files (<a href="http://junit.org" rel="nofollow noreferrer">JUnit</a> tests).  It looked like this:</p>

<pre><code>Project-
  -src/main/java
  -src/test/java
</code></pre>

<p>This way your tests are separate from your source/production code and won't be built/deployed as such.</p>

<p>Going over the Ant documentation I don't really see any convention for this. Am I missing something?  Is there a similar convention in Ant?</p>

My experience with ant -- which is our primary build tool for Java source, so make of this what you will -- is that there are no such
formal
conventions.  Many source projects I've seen organize things in a similar manner; JBoss uses <module>/src/main for sources, etc...  Ant just uses whatever conventions you want, which makes it an ideal tool to integrate into a larger project building framework.
At any rate, the Maven conventions work just fine for Ant, so if you've already got them in place, just re-use the same structures.  Not only is it easier for you to keep track of where things are, when you use a familiar structure, but if you ever decide to mavenize the project, you'll already be set.