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

build: Improved hotswap behavior for the IDE's JVM when executed via the runIde Gradle task. #654

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

SCWells72
Copy link
Contributor

Pretty much what it says in the title. This allows dynamic updates to the running IDE JVM instance for most changes. Changes to class constant values and significant restructuring of Java/Kotlin types will require a JVM restart, but most other changes -- including simple method extractions and such -- will not.

@SCWells72 SCWells72 changed the title Improved hotswap behavior for the IDE's JVM when executed via the runIde Gradle task. build - improved hotswap behavior for the IDE's JVM when executed via the runIde Gradle task. Dec 1, 2024
@fbricon
Copy link
Contributor

fbricon commented Dec 1, 2024

Please rebase your PR against master, we're keeping a linear git history. Merge commits are likely messing up with the conventional commits check

@SCWells72 SCWells72 changed the title build - improved hotswap behavior for the IDE's JVM when executed via the runIde Gradle task. build: Improved hotswap behavior for the IDE's JVM when executed via the runIde Gradle task. Dec 1, 2024
@angelozerr
Copy link
Contributor

I have tried the PR, but I cannot start the plugin:

Caused by: java.lang.VerifyError: Catch type is not a subclass of Throwable in exception handler 57

Execution failed for task ':runIde'.
> Process 'command 'C:\Users\XXXX\.gradle\caches\modules-2\files-2.1\com.jetbrains\jbre\jbr_jcef-17.0.7-windows-x64-b1000.6\extracted\jbr_jcef-17.0.7-windows-x64-b1000.6\bin\java.exe'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 53s
10 actionable tasks: 3 executed, 7 up-to-date
Configuration cache entry stored.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants