Changes between Version 5 and Version 6 of BuildingBase


Ignore:
Timestamp:
Feb 22, 2019, 11:39:06 AM (3 years ago)
Author:
Nicklas Nordborg
Comment:

Added note about JSP compilation (#2151)

Legend:

Unmodified
Added
Removed
Modified
  • BuildingBase

    v5 v6  
    3737{{{ant web jobagent}}}
    3838
    39 All <property>:s defined in `build.xml` can be overridden by creating a file `build.properties` and adding white-space separated key-value pairs
    40 with new property values. It is, for example, needed to set `javac.bootclasspath` to the path to a JRE 6 installation if compiling BASE with Java 7.
    41 See #1635 for more information.
     39All <property>:s defined in `build.xml` can be overridden by creating a file `build.properties` and adding white-space separated key-value pairs with new property values. It is, for example, needed to set `tomcat.home` to the path to a Tomcat installation in order to check that JSP file compile. See below and #2151 for more information.
    4240
    4341=== Main build targets ===
     
    8886    Generate user- and administrator documentation from docbook in HTML format. Docbook will work with pure Java but performance is better if [http://xmlsoft.org/XSLT/ XSLTPROC] is installed. The documentation is generated in the `<base-src>/doc/html` directory.
    8987
     88== Pre-compiling JSP pages ==
     89
     90This should be performed at regular intervals and at least before a new minor release. You need to have Tomcat installation that includes the build tools. If the `${tomcat.home}/bin/catalina-tasks.xml` file is present then you have the correct version. If not, we recommend that the ZIP distribution is downloaded and unpacked to some place. It can be anywhere, you will not have to run an actual Tomcat instance from there.
     91
     92Create a `build.properties` file in your root BASE development directory (=same directory where `build.xml` is located). Add a `tomcat.home` entry that points to the directory where the Tomcat installation is located. The JSP files can then compiled by:
     93
     94{{{
     95ant jsp
     96}}}
     97
     98The goal is that this should compile without errors or warnings. Warnings can be controlled by the `Xlint` parameter. It is by default set to `Xlint:all,-serial`. The `-serial` option is needed since Jasper doesn't create `serialVersionUID` fields in the generated code. The `Xlint` parameter can be customized by setting the `jsp.xlint` property in the `build.properties` file (only the part after `Xlint:`). For example:
     99
     100{{{
     101jsp.xlint all,-serial,-unchecked,-rawtypes,-deprecation,-cast
     102}}}
     103
    90104== Running BASE from the local installation ==
    91105