Team for Capella - Releases 1.4

Team for Capella 1.4.2 (2020-11-06)

Compatibility: Capella 1.4.2

 

What's new

The Team for Capella 1.4.2 maintenance release brings several major changes (compared to Team for Capella 1.4.1):

  • Compatibility with Capella 1.4.2
  • Performances regressions on Collaborative features have been solved in Capella 1.4.2
    • The lazy loading of representations in Team for Capella 1.4.1 was broken by the first creation of a new diagram by a user. 
      • The regression was introduced in 1.4.1 with the new TitleBlock feature even if not used.
    • Some operations might create unwanted Operational Analysis Entities as a silent side effect (Bug 566264).
      • The issue used to occur on OAB diagrams with contextual Operational process allocated to a hierarchy of entities.
      • The Entity elements wrongly generated on each call of the problematic method can cause performance issues. Those elements can be retrieved from the Capella Project Explorer and manually deleted.
      • This issue was present in Capella 1.4.0 and 1.4.1

 

Important notes

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 one fix:

  • The Maintenance application is now compatible with the User Profile mode.

 

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.

 

Team for Capella 1.4.0 (2019-12-20)

CompatibilityCapella 1.4.0

 

What's new

The Team for Capella 1.4.0 major release brings several major changes (compared to Team for Capella 1.3.1):

  • Compatibility with Capella 1.4.0
  • Reduction of the overhead brought by the collaborative features.
  • Improvements of representations lazy loading 
  • A "Locked by" tooltip has been added to the "Diagram is locked" icon visible on the diagram background when its model element is locked.
  • Addition of a Server warmup extension. It allows to read some parts of the database as soon as repositories are started in order to speed up the first access to the data and be close to the time observed on the next access.
  • Addition of a new mode to the Importer application which can now perform the import based on an XML extraction of the repository. In this mode there is no connection to the server and no interaction with other user, this avoids to overload the server.
  • Addition of a new Maintenance application to perform diagnostic and maintenance actions on a repository.
  • Modifications of the Scheduler
    • the new import strategy has been enabled by default in the backup jobs,
    • two new jobs have been added to launch the actions proposed by the Maintenance application.
  • Partial support for internationalization: all literal strings from the runtime part are now externalized and can be localized by third parties by providing the appropriate "language packs" as OSGi fragments
  • Internal optimizations and fixes to improve the stability of collaborative features and the compatibility between Sirius features and the collaborative add-on.

More details can be found in the integrated documentation.

 

Important note

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:

  • Importer application and collaborative features are now more robust against special characters in file paths, logins and passwords
  • Overriding existing remote project is now possible after the use of the cdo export OSGI Command or the use of the Backup database job.
  • A few other minor fixes around collaborative features or the compatibility between Capella features and the collaborative add-on.
  • Documentation minor fixes and improvements