Team for Capella. - Releases 6.1.0
Team for Capella 6.1.0_202509 (2025-09-05)
Compatibility: Capella 6.1.0
What's new
The Team for Capella 6.1.0_202509 maintenance release brings several major changes (compared to Team for Capella 6.1.0):
- Compatibility with Capella 6.1.0
- UX enhancements
- The Semantic Browser refresh computation of referenced elements has been reworked for elements of connected projects. Computation is now done in less than 1s for some projects which used to encounter a 1min freeze on selection change.
- Export wizard has been improved to better handle libraries named with special characters and not yet shared projects.
- Import wizard now correctly sets Library nature for imported libraries
- Images returned by OpenID Connect authentication pages are correctly displayed
- Packaging, installation and deployment
- Some feature patches for Capella 6.1.0 are installed during Team for Capella installation in Capella.
- The update site containing the hot fixes is located in updateSite folder of the Team for Capella bundles.
- It contains the following hotfixes:
- 6.1.0.202306211213 - Client - Avoid deadlock with CheckedPropertyAction (GMF)
- 6.1.0.202407291452 - Client - Richtext Linux/Webkit/Gtk compatibility PoC
- 6.1.0.202409091825 - Client - Avoid deadlock in refresh
- 6.1.0.202410241200 - Client - Sirius adaptation to GMF feature patch
- 6.1.0.202411121700 - Client - Fix NPE in Semantic Browser
- 6.1.0.202411131100 - Client - Avoid infinite loop when pasting image in RichText editor
- 6.1.0.202411141600 - Client - Richtext Linux/Webkit/Gtk compatibility patch update
- 6.1.0.202411201300 - Client - Richtext Linux/Webkit/Gtk compatibility patch update
- 6.1.0.202411281200 - Client - Fix resource display in model tree
- 6.1.0.202502170930 - Client - Avoid NPE in CapellaNavigatorContentProvider
- 6.1.0.202508281230 - Client - Do not dispose system colors in TextRenderer
- Some parameters can now be provided using Java system properties or environment variables, in addition to the previous method.
- Environment variables override the arguments/properties values and Java system properties take precedence over both.
- To ensure compatibility with operating systems that have strict naming conventions, the environment variable is looked up twice: first with the given property name, and then a second time with a modified version of the name (converted to upper case, with dots (.) replaced by underscore (_) and dashes (-) removed).
- For example, both admin.server.jetty.ssl.keystore.passphrase and ADMIN_SERVER_JETTY_SSL_KEYSTORE_PASSPHRASE are accepted as environment variable to provide the parameter via environment variable.
- Here is the list of impacted parameters:
- admin.server.jetty.ssl.keystore.passphrase (takes precedence over the property defined in admin-server.properties)
- admin.server.jetty.ssl.keypassword (takes precedence over the property defined in admin-server.properties)
- ldap.manager.dn (takes precedence over the property defined in ldap-config.properties or equivalent for all repositories)
- ldap.manager.password (takes precedence over the property defined in ldap-config.properties or equivalent for all repositories)
- ldap.truststore.passphrase (takes precedence over the property defined in ldap-config.properties or equivalent for all repositories)
- t4c.database.h2.user (takes precedence over the user defined in dataSource element of all repositories)
- t4c.database.h2.password (takes precedence over the password defined in dataSource element of all repositories)
- Client / CLI tools
- fr.obeo.dsl.viewpoint.collab.https.jetty.ssl.context.passphrase (takes precedence over system property)
- fr.obeo.dsl.viewpoint.collab.credentials.tools.net4j.login (takes precedence over -repositoryLogin, -repositoryCredentials or secureStorage in CLI tools)
- fr.obeo.dsl.viewpoint.collab.credentials.tools.net4j.password (takes precedence over -repositoryLogin, -repositoryCredentials or secureStorage in CLI tools)
- fr.obeo.dsl.viewpoint.collab.credentials.tools.http.login (takes precedence over -httpLogin, -httpCredentials or secureStorage in CLI tools)
- fr.obeo.dsl.viewpoint.collab.credentials.tools.http.password (takes precedence over -httpPassword, -httpCredentials or secureStorage in CLI tools)
- Some feature patches for Capella 6.1.0 are installed during Team for Capella installation in Capella.
- Server changes
- Add capability to list users of static repositories to REST API.
- Complete /users REST API to manage technical users of repositories with OpenID Connect authentication.
- Add OSGI commands to manage CDO revision cache: revisionCacheInfo and revisionCacheCleanup
- Encrypt OpenID Connect authenticator technical users passwords with BCrypt
- Add capability to customize OIDC requests
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.responseType=id_token+token
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.scope=openid+profile+email
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.state=optionalStateEmptyByDefault
- Improve JWT token validation and add capacity to configure access to a repository via token claims
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.complement=&acr_value=xxxXXX (default if not set: empty and not adedd to the request)
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.userInfoPayload=<userInfoEndpoint|access_token|id_token> (default if not set: userInfoEndpoint )
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.userInfoMatchClaim=email (default if not set: name)
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.repositoryFilterPayload=<userInfoEndpoint|access_token|id_token> (default if not set: empty, i.e. no filtering)
- -Dfr.obeo.dsl.viewpoint.collab.server.openid.repositoryFilterMatchClaim=t4c_repository (default if not set: repository)
- Fix wrong CDO revision cache computation
- Encrypt Rest Admin passwords in secure storage with BCrypt
- Server stability has been improved with the correction of a memory leak in CDO revision cache.
- Long commit comment can be truncated if the alternative DB Store is enabled (see cdo-server.xml)
- Update from Jetty 10.0.6 to Jetty 10.0.25
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.