Welcome to JATS
Purpose
The purpose of this WEB page-set is to provide a WEB
based document of the the Utilities provided by JATS.
The information provided in these pages is available
through the JATS command line help system. The web
version may provide an easier reference to the JATS
Utility Documentation.
Scope
The scope of this WEB is the Command Line Utilities that
are provided with JATS.
Specifically this documentation set does not document
the 'build' and 'make' directives that are the heart of
the JATS build system. These are provided in "MASS-00166
JATS Reference Manual".
Overview
JATS is the name of the VIX build tool. It is
instantiated as a command line program, which is really
a wrapper for a collection of tools and utilities. JATS
can be used to:
- Extract files from Version Control
- Build a package
- Place a label on Files under version control
- Transfer the build artifacts into the package repository
- General support the VIX Software Development Process
JATS is machine agnostic. It should work the same on Windows, Solaris and Linux.
JATS is a build system with the following goals:
- Simplify the specification of the build system
The
mechanism by with the user specifies the build
requirements should be described in a high-level
language that is simple to read. Instead of writing
makefiles manually, the programmer populates a template
and lets the build system setup the environment,
generate the makefile and build the application
automatically
- Decouple the build specification from the
implementation.
The build specification should not be
cluttered with the details of the build process. The
user specifies that a library is created from a set of
source files without the need for knowing how this
operation occurs.
- Multi platform support
Builds can be supported on multiple platforms.
Some components may need to be produced for
Solaris, Windows and various embedded environments.
- Multi compiler support
In an embedded environment, many target compilers will
need to be supported. This process should be abstracted
such that the user does not need to know the details of
the operation.
- Simplify the development process
- Uniform build mechanism that allows a package to be
built without any specialised knowledge. This allows:
- Any developer to pick up and build any component.
- Automation of the build process.
References
The following materials are to be used in conjunction with or are referenced by this document.
- Reference
- MASS-00166 JATS Reference Manual
- MASS-00164 Installing and Using JATS
- MASS-00165 JATS configuration files
- DPG-00397 Building and Releasing Packages with JATS
- MASS-00113 Deploylib Reference Manual
- TECHGP-00181 ANT Build Environment
- Tutorials
- Clearcase
- MASS-00230 Basic JATS Tutorial
- TECHGP-00259 Basic JATS Tutorial with SVN
- MASS-00231 Basic JATS Development Environment Tutorial
- Subversion
- TECHGP-00259 Basic JATS Tutorial with Subversion
- TECHGP-00289 Basic JATS Development Environment Tutorial with Subversion
- TECHGP-00290 Branching and Merging with Subversion Tutorial
- General
- MASS-00196 Jats sandbox - Multi Package Development Tutorial
- Misc
- MASS-00099 Generating MUG files with JATS
- MASS-00232 Format of the Linux App Upgrade Manifest File
- MASS-00246 Creating a Debian Package
- TECHGP-00180 Metrics gathering within the Build Environment
- TECHGP-00210 VIX Software Build Overview
- TECHGP-00250 Subversion support within JATS
- TECHGP-00291 Subversion Best Practices
- TECHGP-00299 TechNote - Changes to the use of Subversion
- TECHGP-00253 Creating NSIS Based Windows Installers
- TECHGP-00254 Jats Integration of ZendGuard
- TECHGP-00255 Building Visual Studio Solutions with JATS