| | 1 | = Developers = |
| | 2 | |
| | 3 | == Source Code Management == |
| | 4 | |
| | 5 | The source code of Quest is hosted in a SVN repository. The repository allows anonymous reads. In order to commit something to the repository, you need to authenticate. To get an account, contact [http://www.swe.informatik.uni-goettingen.de/staff/steffen-herbold Steffen Herbold]. The repository URL is: https://quest.informatik.uni-goettingen.de/svn/quest/ |
| | 6 | |
| | 7 | == Build Systems == |
| | 8 | |
| | 9 | * The Java components of Quest use Maven as build and dependency management system. We host a Maven repository that contains the current versions and SNAPSHOTs of quest ([https://trex.informatik.uni-goettingen.de/nexus/]). |
| | 10 | * We develop the Java components with Eclipse and the M2E plug-in. To simplify things for other Eclipse users, we provide Eclipse project configurations in the SVN. This way, a simple SVN checkout is all you need, in order to work with our components and Eclipse. |
| | 11 | * The C/C++ components of Quest written for Windows application. We use Microsoft Visual Studio 2008 to develop and maintain them and provide the required project configurations with the respective projects. |
| | 12 | * For the continuous integration of the Quest components, we use a Hudson server ([https://trex.informatik.uni-goettingen.de/hudson/view/QUEST/]). |
| | 13 | |
