Team for Capella 1.4.1 (2020-07-30)
Compatibility: Capella 1.4.1
What's new
The Team for Capella 1.4.1 maintenance release brings several major changes (compared to Team for Capella 1.4.0):
- Compatibility with Capella 1.4.1
- The documentation has been reorganized around the different roles the team members can have while interacting with Team for Capella: User, Project Administrator, System Administrator, Developer.
- The LDAP authentication support has been completed with the capability to use a manager account when the anonymous binding is disabled.
- The Scheduler configuration has been updated to:
- use a more recent Jenkins version: from LTS version 2.150.2 (LTS) to version 2.204.6 (LTS). This brings several important security fixes and also notable changes as documented in the LTS release notes.
- move from a daily restart of the Team for Capella server to a weekly restart (every Saturday, between 05:00 and 06:00).
- improve the jobs organization: pre-configured jobs have been renamed and grouped in different categories Server Management, Backup and Restore, Diagnostic and Repair, Templates
- The compatibility with other add-ons have been improved with a better management of DFeatureExtension model elements which can be used by those add-ons to store their specific data in the .aird resources.
- A new experimental administration feature is now available for the server, it brings users and repositories management capabilities through REST WebServices and exposes an OpenAPI description.
More details can be found in the integrated documentation.
Important notes
Compatibility with Java 8u261: A new version of the license system and license server (2.6.0) are included in Team for Capella 1.4.1. This avoids a deadlock encountered during attempts to get a token when Team for Capella clients 1.4.0/1.3.2/1.3.1 are launched with Java 8u261.
Windows 10 users: Windows 10 Defender significantly slows down Eclipse, reason being Windows 10 Defender scanning the JAR files. The problem has been reported to Microsoft here. Until then, a workaround to this problem is to add Eclipse root directory to Windows 10 Defender's exclusion list, detailed steps are shared here.
Note: This issue is not specific to Eclipse.
Fixed Issues
This version also introduces several fixes:
- The default repository name can now be overriden with the plugin customization mecanism as it was already the case for the hostname and port
- The Importer application argument management and validation have been improved regarding the different supported import strategies.
- A few other minor fixes around collaborative features or the compatibility between Capella features and the collaborative add-on.