-
Notifications
You must be signed in to change notification settings - Fork 271
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
Cannot use EAP snapshots in 2.0.0-beta5 #1638
Comments
FWIW, you can check my PRs VirtusLab/git-machete-intellij-plugin#1846, VirtusLab/git-machete-intellij-plugin#1859. Still, I haven't got |
In the changelog of beta2, it was noted that we're switching to CDN as a primary source of IntelliJ Platform archives.
This mechanism is still under development and looking at the feedback, I have to make more transparent. |
Thank you! Adding the property to the command:
fixes the build for me! |
I tried the option Instead, it starts the IDE with the JDK I'm using to build the plugin. Reproducible in the template project on the
Is there a way to use the EAP build with the JBR and JCEF? |
You need to add a dependency on JCEF explicitly.
|
Thank you @hsz for the answer. After adding it also to the repository, it now works for me as expected. With the keyword from your answer I also found the matching docs page. I'm still a little surprised I need to specify JBR manually instead of using it manually, as I wouldn't know which other runtime I would use as a plugin developer when running a plugin. |
Apparently the |
Nitpicking: EAP releases work but are officially no longer a primary source of IntelliJ Platform. dependencies {
intellijPlatform {
intellijIdeaCommunity("242-EAP-SNAPSHOT", useInstaller = false)
}
} This is not a workaround. ;-) repositories {
intellijPlatform {
defaultRepositories()
jetbrainsRuntime()
}
}
dependencies {
intellijPlatform {
intellijIdeaCommunity("242-EAP-SNAPSHOT", useInstaller = false)
jetbrainsRuntime()
}
} |
3rd party plugin developers like me are supposed to test our plugins against EAP to have plugin releases available once they [IntelliJ releases] are officially released. This distinction and extra configuration makes it more difficult for me (and I suppose other as well), so it leaves me in an annoyed state as it is diverting my efforts to accidental complexity and technical details. cc: @YannCebron |
For a long time, I've heard that the old dependencies and repositories management is broken. If you plan to use non-default EAP releases, it's good if you understand what you're doing. I've elevated everything to make you change one switch and a missing JBR which is an effect of using IntelliJ Platform artifacts that don't have it bundled.
I'm sorry, but comparing this against closing 95 issues so far, where most of them were not even remotely possible to address in 1.x is a fair deal. |
@hsz - thank you for the work you are putting into this plugin, and thank you for making EAP work. I hope this will find its way into he docs. Let's agree that we then disagree about the "accidental complexity" bit. It also seems that I'm missing how 3rd party developers should test EAP releases given your statement below:
Can you please elaborate how and if you expect 3rd plugin developers to test EAP releases? |
I may be wrong, but we can easily test with EAP Snapshots. It requires some custom code, but you can find the version string from I did this with plugin v1, and now with v2 as I'm not a big fan of how versions are managed in v2 (things are less easy, and they require more boilerplate code, which is like a regression for me, but we already discussed that). My custom code: #1628 (comment) |
What happened?
Timeline for context
242.10180.25
2.0.0-beta4
and then switched to2.0.0-beta5
.2024.1.2
.Problem
I'm trying to ensure that my plugin will be compatible with IntelliJ
2024.2
(which hasn't been released yet), but using EAP builds with the new plugin (2.0.0-beta5
) fails.Relevant log output or stack trace
Steps to reproduce
Specify
242.12881.66-EAP-SNAPSHOT
(built on2024-05-29 06:22:58 UTC
, see snapshot repository), as a platform dependency in the Gradle build script:Run
./gradlew --refresh-dependencies clean buildPlugin
Gradle IntelliJ Plugin version
2.0.0-beta5
Gradle version
8.7
Operating System
Linux
Link to build, i.e. failing GitHub Action job
No response
The text was updated successfully, but these errors were encountered: