- JDK 1.5 or above installed (Required for Maven Eclipse plugin to work properly)
- Eclipse IDE 3.3.x or above- We recommend the version for Java EE developers(Can be downloaded from:http://www.eclipse.org/downloads/)
- Maven M2Eclipse plugin for Eclipse (You can install the latest version from within maven using the following update site from within *Eclipse: http://m2eclipse.sonatype.org/update/)
- SVN Subclipse Plugin Eclipse (Instructions on installing Subclipse plugin can be found here: http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA)
Importing the ESAPI Source
To import the ESAPI source code into your workspace, you can either download the source files in a zip file from here or download the latest trunk from the ESAPI SVN.
The zip files containing the ESAPI source are official releases of the ESAPI. They will be updated whenever major changes are made to the ESAPI, whether features are added/removed, or if ESAPI undergoes a major organizational change. If you are planning on using the ESAPI's reference implementations and want to see ESAPI's source, but do not want to build your own JAR, you might download the ESAPI source zip file (available here).
The ESAPI trunk SVN contains the most up-to-date development version of ESAPI. The trunk may contain different code from the pre-zipped source. It may contain new features or be organized differently. The trunk is a development version of the ESAPI, meaning that contributors to the ESAPI project are actively editing this code, so while all contributors are encouraged to run all test cases on the code before committing it, developers using this code should run their own tests to be sure the code is fully functional. In addition, because the trunk code is in development, documentation regarding the ESAPI, especially Javadocs, may not be entirely accurate.
If you choose to use the ESAPI SVN code, follow the instructions here. Unless you have been added to the ESAPI project as a contributor, please use the bottom SVN checkout link on the Google Code page (non-SSL).
If you are using subclipse, as recommended, open Eclipse and:
- Click File -> New -> Other.....
- From the SVN Folder select '"Checkout Projects from SVN (this option will only be available if you have a SVN plugin installed) and hit Next >.
- Click the Create a new repository location radio button.
- If you are not listed as a project contributor, insert http://owasp-esapi-java.googlecode.com/svn/trunk/ as the URL. If you are listed as a project contributor, check the Google Code page for the URL to use. (Note: if you are a contributor, when prompted for your SVN password, use your Google generated password, available from the Google Code Source page.)
- Once the directory structure appears in the window, click the URL at the top to download everything. Then hit Next >
- Select your desired project options. For most people, the default options should be fine. When finished, click Next >.
- Select your desired workspace options, then click Finish. The latest ESAPI source files will then be downloaded to your workspace. This may take a few minutes.
Some configuration may be necessary for ESAPI to compile and build on your system.
ESAPI requires the Java JRE 5.0+
- Once Java 5.0+ is installed, open the Navigator view in Eclipse. If this is currently hidden, from the toolbar click Window -> Show View -> Navigator.
- Right-click on your ESAPI project in the Navigator, mouse over Maven and click Enable Dependency Management
- Note: If Maven is not an option when you right-click on the project, be sure the Maven plugin for eclipse is installed, as described above.
- Note: If Enable Dependency Management is not an option, dependency management is probably already enabled, So this step can be skipped.
- Right-click on the ESAPI project root folder in the Navigator view and select Properties.
- From the left column, select Java Build Path. Under the Libraries tab, be sure a JRE or JDK is listed next to JRE System Library. If there is a red X on next to the JRE, remove the current JRE and click Add Library and select an alternate JRE. If you are having trouble figuring out what version the current JRE is, select Installed JREs and look at the location to which each version is mapped.
- The Libraries tab should list JRE System Library and Maven Dependencies. If anything else is listed, it is not necessary and should be removed. Maven now handles all dependencies.
- If a red X appears next to Maven Dependencies, click the arrow on the left to expand the tree. If AntiSamy has an error, be sure the script listed above ran without errors.
- From the left column, select Java Compiler. Be sure Compiler compliance level, Generated .class files compatibility, and Source compatibility are all set to 1.5.
- Close the properties window.
- Right-click the ESAPI project root folder and select Refresh.
- From the toolbar, select Project -> Clean.. and select the ESAPI project. Click OK.
- If errors remain, select Maven again, then Update Dependencies.
- ESAPI should now be compiled.
Building ESAPI should be easy with the new Maven integration.
Once your environment is set up, as specified above:
- Right-Click your ESAPI project root folder
- Select Run As...
- Select Run Configurations
- Double Click "Maven Build" from the options on the left to create a new configuration.
- Name your configuration at the top. This will be for building ESAPI without running JUnit tests.
- The "Base directory" should point to the root of your project
- The "Goals" field type "package"
- From the checkboxes below, check "Skip Tests"
- Any options not mentioned should be left as their default
- Click "Apply" to save your build configuration
- Click "Run" to run your configuration
NOTE: There is a bug in Maven Eclipse plugin which does not allow native2ascii to run properly.
To build project using Eclipse we need to point Maven plugin to use our own Maven installation instead of using the embedded.
This can be done as:
- In Eclipse Click Window-->Preferences-->Maven-->Installation-->click add and point to your Maven installation directory. Click ok.
- Goto Run Configuration and select Maven Runtime: External
NOTE: Jars created through building are located in the directory called "target".
Running Test Cases
- From the Navigator view, select test/org/owasp/esapi/AllTests.java
- Right-click -> Run As -> Run Configurations...
- Choose the JUnit configuration
- Select the Arguments tab and enter a VM argument
- -Dorg.owasp.esapi.resources="<path to your esapi project>/test/testresources"
- run tests and verify that they all pass
Running Demo App
The ESAPI Demo application has been named The ESAPI Swingset. More information about Swingset is available here.