Compatibility: Capella 1.2.2
The Team for Capella 1.2.2 maintenance release brings four major changes compared to Team for Capella 1.2.1:
If you move from 1.1.x or from 1.2.0 to this new version, it is recommended to use a new workspace: durable locks have been disabled by default but older versions used to activate this feature as a user choice. It is also possible to clean the old workspace by removing the PREF_ENABLE_DURABLE_LOCKING=true preference value from the workspace metadata located in: .metadata\.plugins\ org.eclipse.core.runtime\.settings\fr.obeo.dsl.viewpoint.collab.prefs file of your workspace.
Since Java 8 U161, some mechanisms used by CDO for the authentication have been deactivated by default for security reasons (JDK-8185292). To ensure that authentication properly works with latest Java releases, the previous behavior is activated with the use of the system property -Djdk.crypto.KeyAgreement.legacyKDF (in the client, the server and the importer).
This version also introduces several fixes:
Compatibility: Capella 1.2.1
The Team for Capella 1.2.1 maintenance release brings four major changes compared to Team for Capella 1.2.0:
For this specific version it is recommended to use a new workspace: durable locks have been disabled by default but older versions used to activate this feature as a user choice. It is also possible to clean the old workspace by removing the PREF_ENABLE_DURABLE_LOCKING=true preference value from the workspace metadata located in: YourWorkspace\.metadata\.plugins\ org.eclipse.core.runtime\.settings\fr.obeo.dsl.viewpoint.collab.prefs
Since Java 8 U161, some mechanisms used by CDO for the authentication have been deactivated by default for security reasons (JDK-8185292). To ensure that authentication properly works with latest Java releases, the previous behavior is activated with the use of the system property -Djdk.crypto.KeyAgreement.legacyKDF (in the client, the server and the importer).
This version also introduces several fixes: