This note describes the state of the AGTEK Access Server development environment as of October 2018. All the server code is written in Java 1.8 and doesn't use any newer language features. In fact 1.8 features are pretty limited to a few instances of lamdas here and there.
The chosen IDE is the Intellij community environment, although Eclipse may still work. Eclipse was the older environment used previously.
There are currently 216 JUnit TestCase test functions in the agteknet/test directory. The best way to test the server is run “TestAll”, which runs all the other test suites. JUnit assert failures will be flagged in the IDE.
NOTE: The production builds run by Jenkins will fail if any unit test fails.
It is highly recommended that all new functionality is coded with unit tests (both at the session level and with client api level) to make sure it works reliably before rolling into either limited testing (e.g. key2) or production. The unit tests also continue to test for deprecated APIs that may still be utilized by older software clients being used by customers.
The following packages (and their versions) are used. Each of these are checked into GIT in the agteknet/packages directory.