Discontinued support for Java < 8
Switch to de.jakop.lotus.domingo hosted on Maven Central and remove checked-in binaries.
0.10.0
The threshold on which the log popup window is shown is now configurable according to the message severity (default ist WARN) (contributed by s-eckey)
Fixed arbitrary NPE while collecting calendar entries from notes (contributed by s-eckey)
0.9.0
Move to Java 7 as minimum required runtime version.
Scheduler state is persisted in the settings file.
0.8.0
Added a scheduler facility in tray mode. The synchronize times can be configured by a cron expression in the settings file. The default interval is 15 minutes.
Supports the command line argument -console, which triggers the synchronization headlessly.
The log window will pop up on new log entries.
A single left click on the tray icon shows or hides the log window.
0.7.2
Added Linux start script.
0.7.1
Fixed problems with different architectures Windows/Linux 32/64-bit.
0.7.1
Starting concurent synchronisations is now prohibited.
The log viewer scrolls to the last logged entry on log change.
0.7.0
Tray icon display beautified with Windows.
Translation of user messages to German is available.
About dialog with version number displayed is available from tray menu.
0.6.0
The application has been given the capabilities to be internationalized. A first translation into english is available.
The license has changed to a friendly BSD license.
0.5.0
For operating systems which support system tray the application now starts in tray mode, which means, it will not start synchronisation immediately but show a tray icon. Right-clicking this icon shows a popup-menu, allowing the user to choose between synchronization, log view and exit. A double click on the icon also triggers synchronisation.
0.4.0
Fixed some bugs.
0.3.1
Fixed bug with appointment types not read from config.
0.3.0
The Lotus Notes installation path is set via configuration file env.properties. For Microsoft Windows it is read from the registry on first start. All other os require the user to provide the path.
0.2.0
The amount of data transferred to Google (title, description, location) is configurable in the settings file. If the event’s title is not transfered, it will be replaced with the event’s type.
The configuration file is upgraded automatically, if there are missing parameters. In this case these parameters are added and a message is prompted, asking the user to verify the default values and to restart.
Fixed a NPE with completely empty Google calendar.
0.1.0
Initial release. Synchronizing works taking start and end dates into account. OAuth2 is used for authentication with Google.
Event’s data is blanked out except type, start and end date.