Difference between revisions of "ESAPI-Building"

From OWASP
Jump to: navigation, search
(Changed directions so ESAPI code is checked out directly into 'ESAPI' directory with no extra 'trunk' directory.)
(Removing steps do download and install AntiSamy locally because it's already available on the Maven Central repository (and the dependency is correctly declared in the POM))
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
ESAPI is easy to build yourself using [http://subversion.tigris.org/ Subversion] and [http://maven.apache.org/ Maven].
+
ESAPI is easy to build yourself using [http://subversion.tigris.org/ Subversion] and [http://maven.apache.org/ Maven]. Ensure that you are using UTF-8 for all source code.
  
 
   $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk ESAPI
 
   $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk ESAPI
 
   $ cd ESAPI
 
   $ cd ESAPI
  $ wget http://owaspantisamy.googlecode.com/files/antisamy-bin.1.3.jar
 
  $ mvn install:install-file -DgroupId=OWASP -DartifactId=AntiSamy -Dversion=1.3 -Dpackaging=jar -Dfile=antisamy-bin.1.3.jar
 
  $ rm antisamy-bin.1.3.jar            # Cleanup after Maven copies to repository.
 
 
   $ mvn -Dmaven.test.skip=true package  # Build ESAPI
 
   $ mvn -Dmaven.test.skip=true package  # Build ESAPI
  

Latest revision as of 08:43, 24 November 2011

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

 $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk ESAPI
 $ cd ESAPI
 $ 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