Git Client IDE plugin known issues

This topic describes the limitations and known issues in the Git Client IDE plugin versions 1.4 and 1.5.

In this topic:

Limitations

The following limitations apply to the Git Client IDE plugin versions 1.4 and 1.5:

  • Stream names must not contain spaces.

  • You may not be able to push changes to a remote repository after using the Git reset command.

  • Dimensions CM projects are not supported.

Back to top

Known issues

Take into account the following known issues when using the Git Client IDE plugin version 1.4 or 1.5:

  • If you use the dimensionshttps or dimensionshttpscac Dimensions CM Git Client protocol with Dimensions CM 14.7 server, you need to update Git configuration files in the git-core folder.

    1. Open the git-core folder.

      Depending on your operating system and the installation path, the location of the git-core folder can be %GIT_HOME%\mingw64\libexec\git-core or /usr/libexec/git-core.

    2. In the the git-core folder, open the start-git-client and git-dm files and find the following line:

      JAVA_OPTS="-Dapple.awt.UIElement=true -Xmx1024m ${DEBUG_JAVA_OPTS}

    3. Replace the line with the following:

      TLS_JAVA_OPTS="-Djdk.tls.client.protocols=TLSv1.3"

      JAVA_OPTS="-Dapple.awt.UIElement=true -Xmx1024m ${DEBUG_JAVA_OPTS} ${TLS_JAVA_OPTS}"

  • Before installing the latest version of the Dimensions CM Git Client IDE plugin, uninstall the earlier versions.
  • When working with topic requests, for any new topic branch you create, you need to check out the topic branch before pushing it to the repository.
  • Git Client IDE plugin 1.5 for NetBeans: When using the GitClient IDE plugin 1.5 with NetBeans on MacOS, the request list does not load.

  • Eclipse 2021+: When you commit and push with a request, you may get the following message in the error log:

    SWT Resource was not properly disposed, SelectRequestDialog.drawHint(SelectRequestDialog.java)

    If this happens, ignore the message. It doesn't affect your operation.

  • Visual Studio 2017: Error messages have limited details.

Back to top

See also: