View source

<iimg>[[JonDo sources]]![[Image:en.png]]</iimg><iimg>[[JonDo sources/de]]![[Image:de.png]]</iimg>
== JonDo Sourcen ==
===Herunterladen der Quellen und JonDo kompilieren===
JonDo ist eine Java-Applikation. Um die Quellen zu übersetzen wird ein Java-JDK und das Build-Tool ''maven2'' benötigt. Die Sourcen werden in zwei gespiegelten SVN-Repositories bereitgestellt (JonDos GmbH, TU Dresden). Für den Download ist ''subversion'' erforderlich.

JonDo besteht aus folgenden Komponenten, die auch einzeln mit ''subversion'' aus den Repositories ausgecheckt und übersetzt werden können:

# '''anonlib''' Die Basis-Bibliothek von JonDo. 
## SVN-Repository der JonDos GmbH: https://svn.jondos.de/svn/anonlib/anonlib/trunk
## SVN-Repository der TU Dresden: https://subversion.inf.tu-dresden.de/svn/anonlib/anonlib/trunk
# '''guilib''' Die GUI-Bibliothek des JonDonym-Projektes. 
## SVN-Repository der JonDos GmbH: https://svn.jondos.de/svn/guilib/guilib/trunk
## SVN-Repository der TU Dresden: https://subversion.inf.tu-dresden.de/svn/guilib/guilib/trunk
# '''logginglib''' Die Logging-Bibliothek des JonDonym-Projektes. 
## SVN-Repository der JonDos GmbH: https://svn.jondos.de/svn/logginglib/logginglib/trunk
## SVN-Repository der TU Dresden: https://subversion.inf.tu-dresden.de/svn/logginglib/logginglib/trunk
# '''JAP''' Das JonDo-Programm. 
## SVN-Repository der JonDos GmbH: https://svn.jondos.de/svn/Jap/Jap/trunk
## SVN-Repository der TU Dresden: https://subversion.inf.tu-dresden.de/svn/Jap/Jap/trunk
## Man kann auch online durch den Quellcode browsen unter: http://anon.inf.tu-dresden.de/develop/doc/jap/ 

Um JonDo aus den Quellen zu erstellen, reicht es aus, nur das letztgenannte JonDo-Programm (Jap) auszuchecken. Das Build-Tool '''maven2''' holt alle weiteren nötigen Bibliotheken und kompiliert sie.

 <code>svn checkout https://svn.jondos.de/svn/Jap/Jap/trunk
 cd trunk
 mvn package</code>

Danach findet man im Unterverzeichnis target die JAR-Datei ''jap-00.xx.yyy-SNAPSHOT-jar-with-dependencies.jar''. Benennen Sie die Datei in JAP.jar um und starten Sie den selbst gebauten JonDo mit: 

 <code>java -jar JAP.jar</code>

===Adding new features to JonDo===
If you want to play with the code or fix some bugs or even add some new features then just do the following. Choose the relevant library and there the proper source file and implement your changes. Afterwards go to the /trunk directory of the library (where the pom.xml) is located and run:
 <code>mvn install</code>
Then go to the /jap/trunk directory and run again
 <code>mvn package</code>
in order to incorporate your new code into the JonDo. This seems quite easy and, indeed, it is provided you avoid some pitfalls:
# Depending on which library your are editing it can be that you have to run "mvn install" in other libraries (and there in the respective /trunk directory) as well in order to get your changes activated. For instance, if you change some code in the ''anonlib'', then it is not enough to run "mvn install" only in its /trunk directory but you have to run it in the ''guilib'' /trunk directory as well before you run "mvn package". The reason is that ''jap'' does not directly depend on the ''anonlib'' but on the ''guilib'' which in turn depends directly on the ''anonlib''. Thus, without running "mvn install" in the ''guilib'' /trunk directory there is a fair chance that an old version of the ''guilib''-library will be used if you are building JonDo, one which does not have your changes included. Therefore, ist is important to check the dependencies in the respective pom.xml files (at least once) before building ''jap''. There is an amount of dependency-tags there which shows the direct dependencies of each library.
# Now that you are aware of all the dependencies there still can go something wrong. The version of the library you improved must match the version used by ''jap'' directly or indirectly. Thus, let's suppose again that you have changed the ''anonlib'' which has version 00.12.015 now (see the version-tag in the respective pom.xml). Suppose further, the ''guilib'' uses version 00.12.014 of the ''anonlib'', i.e. depends on version 00.12.014 of this library (see the respective version-tag within the dependency-tag of the ''guilib'' pom.xml). In this case your changes won't be used by "mvn package" even if you ran "mvn install" on both the ''anonlib'' and the ''guilib''. Therefore, keep in mind to adjust the library's version in the libraries which directly depend on it (that means editing their pom.xml files) to the one your changed library actually has.