Difference between revisions of "ESAPI-Building"

From OWASP
Jump to: navigation, search
m (Added 'cd trunk' between two mvn steps to prevent maven error about 'Cannot execute mojo: ...'.)
(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))
 
(2 intermediate revisions by 2 users 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.
  
   $ mkdir ESAPI
+
   $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk ESAPI
 
   $ cd ESAPI
 
   $ cd ESAPI
  $ svn checkout http://owasp-esapi-java.googlecode.com/svn/trunk
+
   $ mvn -Dmaven.test.skip=true package # Build ESAPI
  $ wget http://owaspantisamy.googlecode.com/files/antisamy-bin.1.3.jar
+
  $ mvn install:install-file -DgroupId=OWASP -DartifactId=AntiSamy -Dversion=1.2 -Dpackaging=jar -Dfile=antisamy-bin.1.3.jar
+
  $ cd 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 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