Removed trouble shooting section (no longer necessary, as issues are fixed).

This commit is contained in:
Achim D. Brucker 2016-09-19 11:10:20 +01:00
parent 4d6b86157c
commit 16743d16f9
1 changed files with 0 additions and 22 deletions

View File

@ -56,28 +56,6 @@ workspace using `File -> Import -> Maven -> Existing Maven Projects`:
While some Wala projects may contain compilation errors, all DASCA
projects (i.e., `eu.aniketos.dasca.*`) should compile without errors.
## Troubleshooting
### Unavailable external JARs
The build process for WALA uses Ant scripts to download JAR libraries
from third-party web sites, which might become unavailable. This leads
to Maven throwing errors when compiling WALA due to unavailable JAR
files, e.g.
```
[ERROR] DASCA/externals/WALA/com.ibm.wala.cast.js.test.data/build.xml:45: Can't get http://ajaxslt.googlecode.com/files/ajaxslt-0-7.tar.gz to DASCA/externals/WALA/com.ibm.wala.cast.js.test.data/temp.folder/ajaxslt-0-7.tar.gz
```
If the affected sub-project is not needed for the DASCA projects (such
as the com.ibm.wala.cast.js.test.data project), the error might be
resolved by skipping the compilation of a few WALA projects, e.g.
```
mvn -P wala -pl '!:com.ibm.wala.cast.js.test.data,!:com.ibm.wala.cast.js.html.nu_validator,!:com.ibm.wala.cast.js.test,!:com.ibm.wala.cast.js.rhino.test' install -DskipTests=true -q
```
### WALA errors
* ``java.lang.Error: unexpected dynamic invoke type 8`` Make sure the
``wala.properties`` file is correctly configured with the path to the
Java 6 JDK. By default, WALA uses the JDK that is runs with also for
the analysis, which is likely to be Java 8.
## Team
Main contact: [Achim D. Brucker](http://www.brucker.ch/)