JUnit on steroids - JUnit in Action - page 441

Table C.2 External JAR/application versions (sorted in alphabetical order)

External project name Version Project URL

Ant 1.7.1 http://ant.apache.org/

Cactus 1.8.1 http://jakarta.apache.org/cactus

Commons BeanUtils http://commons.apache.org/

Commons Collections http://commons.apache.org/

Commons HttpClient http://commons.apache.org/

Commons Logging http://commons.apache.org/

DBUnit 1.5.5 http://dbunit.sourceforge.net/

EasyMock 1.0 http://easymock.org/

Eclipse 3.5.2 http://eclipse.org/

HttpUnit 1.5.3 http://httpunit.sourceforge.net/

Jakarta Taglibs/JSTL 1.0.2 http://jakarta.apache.org/taglibs/

JBoss 4.2.1 http://jboss.org/

Jetty 7.0.0.pre5 http://jetty.mortbay.org/

JUnit 4.6 http://junit.org/

Maven 2.0.10 http://maven.apache.org/

MockObjects 0.09 http://mockobjects.com/

ServletAPI 2.5 http://repo1.maven.org/maven2/javax/servlet/

Tomcat 6.0.14 http://tomcat.apache.org/

C.5 Directory structure conventions

For each project, we followed the directory conventions listed in table C.3.

Table C.3 Directory structure conventions

Directory name Explanation

<project name>/src/main/java Java runtime sources.

<project name>/src/test/java Java test sources.

<project name>/src/main/webapp Web app resources (JSPs, web.xml, taglibs, and so on).

<project name>/src/main/conf Configuration files (if any).

<project name>/target Directory created by the build process (Ant or Maven) to

store generated files and temporary files. It can be safely
deleted, because it's re-created by the build.