BORG Calendar Files

BORG 2.0 is NOT a feature upgrade to BORG. It mainly eliminates third party software that is abandoned, unsupported, or has other issues.

BORG 2.0 is recommended for brand new BORG users and existing users that use Sqlite for the database and do not use CALDAV sync

**** CALDAV users should NOT upgrade to 2.0

BORG 1.0 will continue to be maintained as needed with its current feature set.

BORG 2.0 has the following major changes:

• Remove CALDAV Sync. The third party CALDAV library used by BORG has open issues that have gone unaddressed for over 6 years. It just doesn’t work anymore for many CALDAV servers.

• Remove HSQLDB. 16 years ago, HSQLDB was rewritten and released a new version incompatible with the one BORG uses. BORG 2.0 drops support for HSQLDB. Users can use export/import to switch to Sqlite.

• Upgrade H2 database. 5 years ago, H2 also put out an incompatible upgrade. BORG 2.0 supports the new H2 version, but a MANUAL upgrade using export/import is required for users using H2 currently if they want to move to BORG 2.0.

• Remove Dorkbox system tray. BORG 2_0 will only use the built-in Java system tray.

Google Drive Support

BORG 2.0 contains experimental support for direct access to Google Drive. BORG 2.0 can download its database from Drive if the copy on Drive is newer than the local copy and upload the database back to drive on exit. This eliminates the need for the use of Google Drive sync, which is not supported on Linux.

HSQLDB or H2 users who wish to upgrade should:

• Export your DB in 1.X
• Switch to Sqlite in 1.X
• Run BORG 2.0 and import your DB

H2 users that want to migrate to the newer H2 version (not recommended)

• Export your DB in 1.X
• Go to your database folder and rename or delete your current database file
• Run BORG 2.0 and import your DB