Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 2024 support #5966

Closed
wants to merge 48 commits into from
Closed

Conversation

ahmedyarub
Copy link
Contributor

Checklist

  • I have filed an issue about this change and discussed potential changes with the maintainers.
  • I have received the approval from the maintainers to make this change.
  • This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Issue number: 5965

Description of this change

Enable 2024.1 EAP support.

@github-actions github-actions bot added product: IntelliJ IntelliJ plugin awaiting-review Awaiting review from Bazel team on PRs labels Jan 19, 2024
@sgowroji sgowroji added awaiting-user-response Awaiting response from author on PRs and removed awaiting-review Awaiting review from Bazel team on PRs labels Jan 19, 2024
Tomasz Pasternak and others added 19 commits January 19, 2024 16:07
There are two breaking changes related to MockSdk that come in 2024.1:
1. It is impossible to add a non-JDK SDK to the JdkTable, so the test testChooseDifferentSdkIfCurrentNotJdk
becomes useless and even more impossible to run, because it just fails at preparation phase.
The related IntelliJ change is here:
JetBrains/intellij-community@e8e8cf5#diff-76a3bd6e3df59635af359a63c0936b224dda2f0a80b42ba36236ee4fa85bc09bR55

2. The IdeaTestUtil.getMockJdk no longer returns an instance of MockJdk. It returns a regular JavaSdk instead.
Even more, the MockSdk is officially deprecated. Hence, in 2024.1 and newer we need to Use the regular SDKs
in tests and modify them with SdkModificator

JetBrains/intellij-community@7f05dd0#diff-5fb6bb2bf3104221b2ee04a10cdcf4424ea108b3f541e6b7eb828c721ea8817fL183
…elbuild#5967)

ExtensionPointImpl is now writen in Kotlin and extends Sequence instead of Iterable
Tomasz Pasternak and others added 21 commits January 19, 2024 21:22
There are two breaking changes related to MockSdk that come in 2024.1:
1. It is impossible to add a non-JDK SDK to the JdkTable, so the test testChooseDifferentSdkIfCurrentNotJdk
becomes useless and even more impossible to run, because it just fails at preparation phase.
The related IntelliJ change is here:
JetBrains/intellij-community@e8e8cf5#diff-76a3bd6e3df59635af359a63c0936b224dda2f0a80b42ba36236ee4fa85bc09bR55

2. The IdeaTestUtil.getMockJdk no longer returns an instance of MockJdk. It returns a regular JavaSdk instead.
Even more, the MockSdk is officially deprecated. Hence, in 2024.1 and newer we need to Use the regular SDKs
in tests and modify them with SdkModificator

JetBrains/intellij-community@7f05dd0#diff-5fb6bb2bf3104221b2ee04a10cdcf4424ea108b3f541e6b7eb828c721ea8817fL183
…llij into ay/2024.1_eap

# Conflicts:
#	java/tests/integrationtests/com/google/idea/blaze/java/sync/projectstructure/JdksTest.java
There are two breaking changes related to MockSdk that come in 2024.1:
1. It is impossible to add a non-JDK SDK to the JdkTable, so the test testChooseDifferentSdkIfCurrentNotJdk
becomes useless and even more impossible to run, because it just fails at preparation phase.
The related IntelliJ change is here:
JetBrains/intellij-community@e8e8cf5#diff-76a3bd6e3df59635af359a63c0936b224dda2f0a80b42ba36236ee4fa85bc09bR55

2. The IdeaTestUtil.getMockJdk no longer returns an instance of MockJdk. It returns a regular JavaSdk instead.
Even more, the MockSdk is officially deprecated. Hence, in 2024.1 and newer we need to Use the regular SDKs
in tests and modify them with SdkModificator

JetBrains/intellij-community@7f05dd0#diff-5fb6bb2bf3104221b2ee04a10cdcf4424ea108b3f541e6b7eb828c721ea8817fL183
…llij into ay/2024.1_eap

# Conflicts:
#	testing/BUILD
…llij into ay/2024.1_eap

# Conflicts:
#	common/util/BUILD
#	intellij_platform_sdk/build_defs.bzl
#	java/BUILD
#	third_party/go/BUILD
…llij into ay/2024.1_eap

# Conflicts:
#	intellij_platform_sdk/build_defs.bzl
#	java/BUILD
#	testing/testcompat/v241/com/google/idea/sdkcompat/BaseSdkTestCompat.java
#	third_party/go/BUILD
@ahmedyarub ahmedyarub marked this pull request as ready for review January 20, 2024 17:46
@github-actions github-actions bot added product: CLion CLion plugin product: GoLand GoLand plugin awaiting-review Awaiting review from Bazel team on PRs labels Jan 20, 2024
@agluszak
Copy link
Collaborator

Let's just wait for @tpasternak to finish his PR

@agluszak agluszak closed this Jan 20, 2024
@github-actions github-actions bot removed the awaiting-review Awaiting review from Bazel team on PRs label Jan 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-user-response Awaiting response from author on PRs product: CLion CLion plugin product: GoLand GoLand plugin product: IntelliJ IntelliJ plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants