This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "ESAPI-Building"

From OWASP
Jump to: navigation, search
m (Change references from using svn and Google Code to git and GitHub.)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Simple Build Instructions==
+
ESAPI is easy to build yourself using [https://git-scm.com/ Git] and [http://maven.apache.org/ Maven]. Ensure that you are using UTF-8 for all source code.
  
ESAPI is easy to build yourself using [http://subversion.tigris.org/ Subversion] and [http://maven.apache.org/ Maven].
+
  $ git clone https://github.com/ESAPI/esapi-java-legacy.git    # This will clone the 'develop' branch.
 
+
   $ cd esapi-java-legacy
  $ mkdir ESAPI
+
   $ mvn -Dmaven.test.skip=true package # Build ESAPI
   $ cd ESAPI
 
  $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk
 
   $ mvn -Dmaven.test.skip=true package
 
  
 
Maven will generate a "target" directory that contains the ESAPI jar file.
 
Maven will generate a "target" directory that contains the ESAPI jar file.

Latest revision as of 05:30, 9 February 2016

ESAPI is easy to build yourself using Git and Maven. Ensure that you are using UTF-8 for all source code.

 $ git clone https://github.com/ESAPI/esapi-java-legacy.git    # This will clone the 'develop' branch.
 $ cd esapi-java-legacy
 $ mvn -Dmaven.test.skip=true package  # Build ESAPI

Maven will generate a "target" directory that contains the ESAPI jar file.

To generate project reports use:

 $ mvn site

To generate documentation use:

 $ mvn javadoc:jar