Update authored by Bernhard Johannes Berger's avatar Bernhard Johannes Berger
......@@ -34,22 +34,24 @@ For using the changes in the EvoAl execution environment, you have to install yo
The `flatten:flatten` parameter is necessary to replace some variables used in the `pom.xml` files by their concrete values to allow the downstream maven projects (those from the EvoAl execution environment) to use them without problems.
## Changing EvoAl Execution Environment
You can find the EvoAl execution runtime in the `src/evoal` folder in the repository.
You can find the source code of the EvoAl execution runtime in the `$EVOAL_REPO/src/evoal` folder in the repository.
There you will do all your local changes.
When testing your changes, you have to create a local release, which you can create automatically and can be found in `$EVOAL_REPO/evoal`.
### Setting up IntelliJ
Simply import the parent project from `src/evoal`.
Simply import the parent project from `$EVOAL_REPO/src/evoal`.
### Changing the Code
Simply use IntelliJ to change the code.
### Creating a Local Execution Environment
To create an execution environment that include your changes you first have to execute `mvn package` in the `src/evoal` folder.
This step will create a plugin folder in the `target` folder of every maven plugin.
Then, you execute the script `ci/create-release.sh` in the root folder of your repository.
This script will create a local release in the folder `evoal`.
To create an execution environment that include your changes you first have to execute `mvn package` in the `$EVOAL_REPO/src/evoal` folder.
This step will create a plugin folder in the `target` folder of every Maven plugin.
Then, you execute the script `$EVOAL_REPO/ci/create-release.sh` in the root folder of your repository.
This script will create a local release in the folder `$EVOAL_REPO/evoal`.
***Note:*** If you don't want to create a release every time you are doing a change, you
can simply add a symbolic link from `src/evoal/..../target/<plugin-name>` to `evoal/plugins/<plugin-name>`. Then it is only necessary to execute `mvn package` to update your plugin.
can simply add a symbolic link from `$EVOAL_REPO/src/evoal/plugins/.../target/<plugin-name>` to `$EVOAL_REPO/evoal/plugins/<plugin-name>`. Then it is only necessary to execute `mvn package` to update your plugin.
### Logging and Debugging of EvoAl Exution Environment
You can set the environment variable `EVOAL_LOGGING` in your execution shell to a logging level (`error`, `warn`, `info`, `debug`) to turn on logging in EvoAl. If you want to debug your plugin, you can set the environment variable to `EVOAL_DEBUG` to `true` to start the execution environment in the debug mode. Using any EvoAl script will result in starting the execution environment and make it wait for a debugger. You can attach your IntelliJ by selecting "Attach to ...". Then you can simply debug the application.
\ No newline at end of file