• Home
• de.opal-project
• opal-developer-tools_2.11
• 0.8.15
• source code

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

ct.opal-developer-tools_2.11.0.8.15.source-code.README.markdown Maven / Gradle / Ivy

# Overview

## application.conf
Static configuration of all available queries as well as further global settings.

## hermes.json
The configuration file which is used to specify the projects which belong to a test corpus. By default, the projects are specified which belong to OPAL's test corpus. To evaluate another corpus just adapt this file. Basically every project has the following settings: `id`, `cp`, `libcp` and `libcp_defaults`.

### `id`
`id` specifies the unique name of the project.

### `cp`
`cp` specifies the class path of the project that references all classes that are developed as part of the project.
It is possible to specify multiple folders/jars by separating them using the system's folder separator (on Mac: `:`).

### `libcp` and `libcp_defaults`(Optional)
These parameters specify the used libraries that should be loaded.
The latter two settings are particularly required by more advanced queries which, e.g., require a complete class hierarchy.
`libcp_defaults` is used to specify that some generally available APIs should be added to the class path.
Currently, the keys `JRE` and `RTJar` are predefined and will always resolve against the current ***JRE***/the ***rt.jar***.

    {
      "id": "OPAL-bytecode-infrastructure_2.11-SNAPSHOT-08-14-2014",
      "cp": "../../OPAL/bi/src/test/resources/classfiles/OPAL-bytecode-infrastructure_2.11-SNAPSHOT-08-14-2014.jar",
      "libcp": "../../OPAL/bi/src/test/resources/classfiles/OPAL-common_2.11-SNAPSHOT-08-14-2014.jar"
      "libcp_defaults" : ["JRE"]
    }

## Note
The split between both files was purely done to provide some structure and to facilitate reuse. All settings defined in application.conf can also be set in Hermes.json. It is in particular possible to turn of or add new queries by specifying them in hermes.json.