| ... | ... | @@ -30,11 +30,7 @@ Some toolboxes of the SDK4ED Platform impose some additional limitations and pre |
|
|
|
- <ins>C/C++ Projects:</ins> No prerequisites or limitations
|
|
|
|
- <ins>Java Projects:</ins> The binary (i.e., compiled) files of the source code of the software project should be also uploaded on the Git repository. The user should upload either the .class files that are produced after the compilation of the software project, or the final JAR (or WAR) file of the software project.
|
|
|
|
- TD Toolbox:
|
|
|
|
- <ins>C/C++ Projects:</ins> No prerequisites or limitations
|
|
|
|
- <ins>Java Projects:</ins>
|
|
|
|
- The user must create a folder named "jars" and inside this folder, he/she should place the jar file of the code.
|
|
|
|
- TD Analysis toolbox, analyses versions not commits. So for each commit that is version, you should include the jar file.
|
|
|
|
- In addition, the name of the jar file should be the same as the Git project's name followed by the number of version e.g. projectName0.jar for the project with title "projectName" and version 0 (the first version), projectName1.jar for the version 1 (the second version) and so on. The projectName is the Git repo name (without “/” and “.git” for example for project
|
|
|
|
- <ins>TD Analysis toolbox, analyses releases not commits. So if there are no releases on the repository it will analyse 10 commits.</ins>
|
|
|
|
- Energy Toolbox:
|
|
|
|
- A config.txt file must be added in the root directory with the following format (all the paths starting from the root directory of the repo):
|
|
|
|
```
|
| ... | ... | |
