Changes between Version 2 and Version 3 of BuildingBase

Jun 15, 2011, 12:08:17 PM (13 years ago)
Nicklas Nordborg

Finished the Building BASE page


  • BuildingBase

    v2 v3  
    7 == Getting the source code ==
     7== 1. Getting the source code ==
    99=== Download ===
    1919This will create a sub-directory `base-src` with all source files. Anonymous checkouts are allowed, but write permission is only granted to developers. The trunk version is the head of the development and should be used for testing purposes only. The sub-urls to `*` and `*` can be used to get other version, including specific releases and bugfix branches. For more information see the DownloadPage or check the [/browser subversion source repository] directly.
     21== 2. Create a local configuration ==
     23The configuration files included with a binary distribution are located in the `<base-src>/config/dist` directory. You should never modify these files directly for your local setup. Instead, place a copy of files that you need to modify in the `<base-src>/config/local` directory. When building BASE all targets exception the 'dist' target will first check the local configuration files.
     25Note that the build process usually copies the configuration files to the `<base-src>/www/WEB-INF/classes` directory. The reason is that Tomcat can't read files outside the `WEB-INF` directory and this makes the subversion working copy identical to a binary distribution.
     27 * All utility programs, such as the installation program and the job agent, use the configuration files in `<base-src>/www/WEB-INF/classes`.
     28 * The only exception is the test programs. They will read the configuration from `<base-src>/config/local` and `<base-src>/config/dist` directories.
     29 * Running `ant clean` will remove the copied configuration files.
     31== 3. Ant ==
     33We use [ Ant] to build and compile BASE. You will need at least version 1.8. All build instructions for Ant are in the build.xml file.
     35A build is started with the command:
     37{{{ ant <target> }}}
     39where `<target>` is one of the named targets defined in the build file. You may specify multiple targets:
     41{{{ant web jobagent}}}
     43=== Main build targets ===
     45These targets works on the entire BASE source code. They may take some time to finish, but everything will be checked and recompiled if needed.
     47`ant dev`
     48    Build everything for local use. This targets compiles the core, plugins, web application, job agent, etc. for local use. It doesn't generate javadoc documentation.
     50`ant dist`
     51    Build everything for distribution. This target compiles everything, generates the javadoc documentation, etc. Everything is placed in the dist subdirectory.
     53`ant package`
     54    Create compressed tar files of the distribution.
     56`ant clean`
     57    Remove all generated files.
     59=== Other useful targets ===
     61These targets are quicker to use if you know that you have only made changes to a specific module.
     63`ant core`
     64    Compile the core for local use.
     66`ant coreplugins`
     67    Compile the core plugins for local use.
     69`ant web`
     70    Compile the web client application for local use.
     72`ant installprg`
     73    Compile the installation programs for local use.
     75`ant jobagent`
     76    Compile the job agent for local use.
     78`ant test`
     79    Compile the test programs for local use.
     81`ant doc`
     82    Generate documentation for local use. This generates all documentation and may take a long time.
     84`ant doc.javadoc`
     85    Generate Javadoc documentation only. The documentation is generated in the `<base-src>/doc/api` directory.
     87`ant doc.docbook.html`
     88    Generate user- and administrator documentation from docbook in HTML format. Docbook will work with pure Java but performance is better if [ XSLTPROC] is installed. The documentation is generated in the `<base-src>/doc/html` directory.
     90== Running BASE from the local installation ==
     92If you have followed the instructions so far the subversion working copy installation is compatible with a binary distribution. You canfind the installation programs, web application and all other things in the same places as for a binary installation. Read the [/chrome/site/latest/html/admindoc/installation_upgrade/installation_upgrade.html installation instructions] for more information.