Directory Organization in CVS

Let's assume all the directory mentioned below are all under the CVS PatternTesting module directory.

NameDescription
xdocs Location of XML documentation (transformed to HTML by Maven)
testsuites Contains all Aspect Test suites for different application domains: Standard Java, EJB, Avalon, etc. Each of these domain is what we call a TestSuite. They are Maven subprojects and they deliver separate distributables so that someone interest in Avalon Pattern Tests will only need to use the Pattern Tests related to Avalon. Each TestSuite has its own web site to describe the pattern tests it implements.
plugins Some plugins for Pattern Tests. For example: A JUnit plugin that allow to test pattern tests that are applied at compile time, a Maven Plugin for running Pattern Test on a Maven project, etc.
target Temporary directory created by the build process. It must not be committed to CVS.

All projects and subprojects are Maven projects and thus follow the Maven directory structure.

Example of TestSuites:

NameDescription
testsuites/java TestSuite related to general java pattern tests. For example verifying that no System.out.println is used, etc.
testsuites/avalon TestSuite related to Avalon pattern tests. For example verifying that no a Thread Safe component cannot set an instance variable in any method other than compose() and initialize().
testsuites/ejb TestSuite related to EJB pattern tests. For example verifying that all EJBs behind a SLSB facade one are all Local EJBs.