OpenGTS sources in Eclipse

The OpenGTS section you are currently reading (OpenGTS menu from top to this point) has gone through compilation, deployment and configuration without touching the Java Source Code. In order to combine the OpenGTS sources with the ROAF sources both need to be available in an Development Environment in order to trace stacks.

In the OpenGTS documentation you can find one approach to install the sources similar to the original OpenGTS installation (OpenGTS_Eclipse.pdf: How to Use Eclipse with OpenGTS written by P. Bucolo). This document is instructing to apply the ant process from inside Eclipse.

The documentation you are currently reading considers ant as a deployment and Eclipse as a development tool in different environmentsSince every developer has his own way to handle source code these pages are meant to provide an orientation for OpenGTS development. In team development it is obligatory to use a central code depository of a versioning system. The following is simply describing how to install dedicated source packages for personal studies and modifications. From there on every developer should be able to apply versioning and set up team development.

Prerequisites

As pointed out at several OpenGTS pages on this site: This site is (currently) describing how to dig into the OpenGTS code. It is a prerequisite that you have installed OpenGTS and published the track.war in Tomcat on your developer machine (as described in OpenGTS_Config.pdf) before installing the Eclipse IDE. In other words the checkInstall skript should be executable at all times to verify the correct installation of the OpenGTS components:

Environment variable paths (canonical):
  GTS_HOME               ==> C:\prox\OpenGTS_2.4.1
  GTS_CONF               ==> C:\prox\OpenGTS_2.4.1\default.conf
  JAVA_HOME              ==> C:\prox\Java\jdk1.6.0_32
  ANT_HOME               ==> C:\prox\apache-ant-1.8.3
  CATALINA_HOME          ==> C:\prox\apache-tomcat-7.0.27
Extended library Jar files: 'java.ext.dirs'
  (Ext dir)              ==> C:\prox\Java\jdk1.6.0_32\jre\lib\ext
  mail.jar               ==> Found 'mail.jar'
  mysql-connector-java-* ==> Found 'mysql-connector-java-5.1.20-bin.jar'
Runtime Configuration:
  (Default cfg dir)      ==> C:\prox\OpenGTS_2.4.1
  (Default cfg file)     ==> C:\prox\OpenGTS_2.4.1\default.conf
  (WebApp cfg file)      ==> C:\prox\OpenGTS_2.4.1\webapp.conf
  log.dir                ==> C:\prox\OpenGTS_2.4.1\logs
  db.sql.provider        ==> mysql
  db.sql.host            ==> localhost
  db.sql.dbname          ==> gts
  db.sql.user            ==> gts
  db.sql.utf8            ==> true
  db.sql.url             ==> jdbc:mysql://localhost:3306/
reports.xml:
  (XML file)             ==> C:\prox\OpenGTS_2.4.1\reports.xml
private.xml:
  (XML file)             ==> C:\prox\OpenGTS_2.4.1\private.xml
  (Class)                ==> org.opengts.war.tools.PrivateLabelLoader
=============================================================
No errors reported
No warnings reported
=============================================================

Besides a Java Compiler with JavaMail, the Tomcat Container, a MySQL database engine with a JDBC driver you should also test the track.war frontend with an installed 'gts' user and database with an account, (user, ) device and some event data. Actually it is advised to create an OpenGTS sql dump (for example with the MySQL workbench) at an early stage. This dump can replace the database initialization described in OpenGTS_Config.pdf - the next time you want to set up a new installation.

Although ant is part of the Eclipse installation it will not be executed from Eclipse and you should make sure that the ant all process can be launched utilizing the environment variables listed above. The GTS_HOME can be perceived as the code base of the original code. The IDE will be used to 'check out' (copy) this code to be analyzed and modified. After modification it is up to you to merge the code back to GTS_HOME/src (and other directories) and run the ant all deployment.

After running checkInstall (on the original build.xml or buildLite.xml) with

No errors reported
No warnings reported

 you are ready to goto the next page to install Eclipse.

 

 « configuration install Eclipse »