Rev 361 | Rev 1447 | Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | RSS feed
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head><title>Welcome to JATS</title><link rel="stylesheet" href="Jats.css" type="text/css" /><meta http-equiv="content-type" content="text/html; charset=utf-8" /></head><body><h1>Welcome to JATS</h1><h2>Purpose</h2>The purpose of this WEB page-set is to provide a WEBbased document of the the Utilities provided by JATS.The information provided in these pages is availablethrough the JATS command line help system. The webversion may provide an easier reference to the JATSUtility Documentation.<h2>Scope</h2>The scope of this WEB is the Command Line Utilities thatare provided with JATS.Specifically this documentation set does not documentthe 'build' and 'make' directives that are the heart ofthe JATS build system. These are provided in "MASS-00166JATS Reference Manual".<h2>Overview</h2>JATS is the name of the ERG build tool. It isinstantiated as a command line program, which is reallya wrapper for a collection of tools and utilities. JATScan be used to:<ul><li>Extract files from Version Control<li>Build a package<li>Place a label on Files under version control<li>Transfer the build artifacts into the package repository<li>General support the ERG Software Development Process</ul>JATS is machine agnostic. It should work the same on Windows, Solaris and Linux.JATS is a build system with the following goals:<ul><li> Simplify the specification of the build system<br>Themechanism by with the user specifies the buildrequirements should be described in a high-levellanguage that is simple to read. Instead of writingmakefiles manually, the programmer populates a templateand lets the build system setup the environment,generate the makefile and build the applicationautomatically<li> Decouple the build specification from theimplementation.<br>The build specification should not becluttered with the details of the build process. Theuser specifies that a library is created from a set ofsource files without the need for knowing how thisoperation occurs.<li> Multi platform support<br>Builds can be supported on multiple platforms.<br>Some components may need to be produced forSolaris, Windows and various embedded environments.<li> Multi compiler supportIn an embedded environment, many target compilers willneed to be supported. This process should be abstractedsuch that the user does not need to know the details ofthe operation.<li>Simplify the development process<li>Uniform build mechanism that allows a package to bebuilt without any specialised knowledge. This allows:<ul><li>Any developer to pick up and build any component.<li>Automation of the build process.</ul></ul><h2>References</h2>The following materials are to be used in conjunction with or are referenced by this document.<br><ul><li>Reference<ul><li> MASS-00166 JATS Reference Manual<li> MASS-00164 Installing and Using JATS<li> MASS-00165 JATS configuration files<li> DPG-00397 Building and Releasing Packages with JATS<li> MASS-00113 Deploylib Reference Manual<li> TECHGP-00181 ANT Build Environment</ul><li>Tutorials<ul><li> MASS-00230 Basic JATS Tutorial<li> TECHGP-00259 Basic JATS Tutorial with SVN<li> MASS-00231 Basic JATS Development Environment Tutorial<li> MASS-00196 Jats sandbox - Multi Package Development Tutorial</ul><li>Misc<ul><li> MASS-00099 Generating MUG files with JATS<li> MASS-00232 Format of the Linux App Upgrade Manifest File<li> MASS-00246 Creating a Debian Package<li> TECHGP-00180 Metrics gathering within the Build Environment<li> TECHGP-00210 ERG Software Build Overview<li> TECHGP-00250 Subversion support within JATS<li> TECHGP-00253 Creating NSIS Based Windows Installers<li> TECHGP-00254 Jats Integration of ZendGuard<li> TECHGP-00255 Building Visual Studio Solutions with JATS</ul></ul></body></html>