Merge branch 'master' of https://github.com/WebFuzzing/EvoMaster into enable-new-security

Author: arcuri82

.github/workflows/release.yml

@@ -11,6 +11,7 @@ env:
   evomaster-version: 5.1.1
   jdk-jar: 17
   jdk-jpackage: 21
+  java-distribution: temurin
   retention-days: 1
 ## Doesn't work, ie, use env in env
 #  installer-windows: evomaster-${evomaster-version}.msi
@@ -24,9 +25,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Setup JDK ${{env.jdk-jar}}
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v5
         with:
           java-version: ${{env.jdk-jar}}
+          distribution: ${{env.java-distribution}}
       - name: Cache Maven packages
         uses: actions/cache@v3
         with:
@@ -74,9 +76,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Setup JDK ${{env.jdk-jpackage}}
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v5
         with:
           java-version: ${{env.jdk-jpackage}}
+          distribution: ${{env.java-distribution}}
       - name: Download fat jar
         uses: actions/download-artifact@v4
         with:
@@ -99,9 +102,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Setup JDK ${{env.jdk-jpackage}}
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v5
         with:
           java-version: ${{env.jdk-jpackage}}
+          distribution: ${{env.java-distribution}}
       - name: Download fat jar
         uses: actions/download-artifact@v4
         with:
@@ -124,9 +128,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Setup JDK ${{env.jdk-jpackage}}
-        uses: actions/setup-java@v1
+        uses: actions/setup-java@v5
         with:
           java-version: ${{env.jdk-jpackage}}
+          distribution: ${{env.java-distribution}}
       - name: Download fat jar
         uses: actions/download-artifact@v4
         with:

README.md

@@ -285,6 +285,7 @@ Otherwise, if you are working in industry on closed-source APIs, we have options
 * [Library dependencies for the generated tests](docs/library_dependencies.md)
 * [How to contribute](docs/contribute.md)
   * [Technical notes for developers contributing to EvoMaster](docs/for_developers.md)
+  * [Notes for MSc/BSc students doing their theses/projects with EvoMaster](docs/for_msc_bsc_students.md)
 * Troubleshooting
   * [Windows and networking](docs/troubleshooting/windows.md)
   * [java.lang.OutOfMemoryError](docs/troubleshooting/outofmemory.md)

docs/for_msc_bsc_students.md

@@ -0,0 +1,22 @@
+## NOTES FOR MSc/BSc STUDENTS
+
+Welcome to EvoMaster!!!
+
+It is great that you are going to do a MSc/BSc project with EvoMaster. 
+We wish this is going to be an exciting experience for your professional development and growth. 
+
+In this document, let us summarize some practical process aspects of your involvement with EvoMaster:
+
+* You start to work on your own Git _fork_. When your first feature/unit-of-development is ready for a Pull Request (PR), you do a PR towards the main repository of EvoMaster. 
+
+* Before making a PR, make sure __all test cases pass__ on your fork's Continuous Integration (CI), i.e., currently GitHub Actions. Also, make sure to pull from latest _master_ branch of EvoMaster before making the PR. 
+
+* On GitHub's interfaces, ask for review of your PR to your direct academic supervisor (e.g., Prof. Galeotti if you are studying in Argentina, Dr. Zhang if in China, or Dr. Sahin if in Türkiye). When you fix the comments of your supervisor, and your supervisor approves your PR, your supervisor will ask for review to the current EvoMaster's [benevolent dictator](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life) (i.e., Prof. Arcuri, in Norway).  
+
+* A PR from a fork is never going to be merged directly into the _master_ branch. It will first be merged into a new branch. The problem is on how CI is currently setup (long story...). When CI is green on the new branch, it will be merged into _master_. 
+
+* When your first PR is merged into _master_, time to celebrate! Thanks for your contribution ;) You will get access to EvoMaster' repository with _write_ rights. From now on, you discard your fork, and work directly in the EvoMaster's repository. 
+
+* The _master_ branch of EvoMaster is protected. You cannot directly modify it. You need to work on branches, and then make PRs, using the same process: CI needs to be green before you ask your direct supervisor for review, which will then ask the "dictator" for a second review. 
+
+* When making PRs, please remember that _small is beautiful_. If you can divide your work in small separated units that can be reviewed separately, that would be better than a 10k-50k LOCs single PR... also, a feature does not need to be fully completed before some code start to get merged via PRs (as long as CI is green, of course).