This page last changed on Dec 29, 2005 by vmassol.
Cargo's directory organization can be daunting for a newcomer. So here's some information on how the project is organized.
 | Legend
- directory/ : represents a directory
- directory/ : represents a directory containing a Maven project
|
- cargo/
- core/ : Core Java APIs
- api/
- util/ : Some useful classes for both module/ and container/ (logging interface, etc)
- module/ : API to create/parse J2EE Module files
- container/ : API to start/stop/configure containers and deploy J2EE Modules in them
- generic/ : Generic and untyped Java API sitting on top of the Core Container Java API
- containers/
- resin/ : Resin implementation
- tomcat/ : Tomcat implementation
- .../ : Other container implementations
- uberjar/ : Uberjar packaging all api/ and containers/ jars in one big jar
- build-tools/ : Common files and tools related to the Maven 1 and Maven 2 builds (common checkstyle files, etc).
- extensions/ : Cargo extensions
- ant/ : Ant tasks that uses the core/ projects API
- maven/ : Maven 1 plugin (based on the Ant tasks)
- maven2/ : Maven 2 plugin
- netbeans/ : Netbeans plugin
- intellijidea/ : IntellijJ IDEA plugin
- samples/ : Sample projects that also serve as functional tests
- java/ : Samples exercising the Java core API
- extensions/
- ant/ : Samples exercising the Ant tasks
- maven/ : Samples exercising the Maven 1 plugin
- maven2/ : Samples exercising the Maven 2 plugin
- testdata/ : Test data for all the Sample projects
- authentication-war : Generates WAR with BASIC authentication defined in web.xml
- empty-ear : Generates en empty EAR
- empty-jar : Generates en empty JAR
- expanded-war : Generates an expanded WAR
- simple-ear : Generates a simple EAR containing a simple WAR
- simple-war : Generates a simple WAR containing an HTML file
- tomcat-context : Generates a WAR containing a Tomcat context.xml file redefining the Context Root
|