Integration Server 10.3 | VCS Integration Feature Configuration Guide | Overview | Understanding Package, Element, and File Behavior | Package Contents and Interaction with the VCS Integration Feature | \code Directory
 
\code Directory
This directory does not normally contain files, only subdirectories that hold the source and executable code for coded services (that is, Java, C/C++, and COM services).
Subdirectory
Contents
VCS Integration
\code\jars
External Java libraries used by the services in the package.
You must manually check in and check out files in this directory using your VCS client.
\code\libs
All executable C/C++ and/or COM program files that belong to the package. These files can be one of the following:
*Third-party C/C++ or COM libraries used by services in this package
*Libraries and/or executable files for services that you have developed using C/C++ and/or COM
You must manually check in and check out files in this directory using your VCS client.
\code\classes
Java class files for services that belong to the package.
You must manually check in and check out files in this directory using your VCS client. Generated code is not usually version controlled.
\code\source
Source files for coded services (Java services, C/C++ services, and COM services) that belong to the package.
If the package contains Java services, this directory will have one source file for each folder that contains Java services. This file holds the source code (as a single class) for all of the Java services (coded as methods of the class) in the folder.
Some files in this directory are automatically checked in and checked out by the VCS Integration feature:
*Files for Java services are checked in and out by the VCS Integration feature.
*C/C++ or COM services are added to the VCS repository when they are created; after that, they must be manually checked in and checked out.