You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm kind of stuck between Gretty and IntelliJ, trying to figure out how to proceed :)
I work with IntelliJ and I maintain a project that uses Gretty for development purposes. Up until recently, I've been using this workaround to launch Gretty and a debug session in one click, but now that workaround is not viable anymore.
Starting with IntelliJ 2018, the init script it creates to launch Gradle tasks can't be parsed to get the JVM args that IntelliJ injects to get the debugging session work. This is an example of such an init script taken from an IntelliJ Ultimate v2018.2:
Notice how it checks if the task extends JavaForkOptions to inject the output of the ForkedDebuggerHelper.setupDebugger call.
This ForkedDebuggerHelper builds a JVM args string like this: -agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=12345, which links the gradle task with the debugger session IntelliJ has set up.
Since Gretty tasks appRunWar, etc. don't implement JavaForkOptions, it is impossible to get a debugging session without recurring to other tasks like appRunWarDebug and starting a remote debug session.
It's great that we can start a remote debugging session, but I wonder if all app* tasks could implement JavaForkOptions like other standard Gradle tasks. This would be very useful for people like me, that work with IntelliJ.
The text was updated successfully, but these errors were encountered:
Hi! I'm kind of stuck between Gretty and IntelliJ, trying to figure out how to proceed :)
I work with IntelliJ and I maintain a project that uses Gretty for development purposes. Up until recently, I've been using this workaround to launch Gretty and a debug session in one click, but now that workaround is not viable anymore.
Starting with IntelliJ 2018, the init script it creates to launch Gradle tasks can't be parsed to get the JVM args that IntelliJ injects to get the debugging session work. This is an example of such an init script taken from an IntelliJ Ultimate v2018.2:
Notice how it checks if the task extends
JavaForkOptions
to inject the output of theForkedDebuggerHelper.setupDebugger
call.This
ForkedDebuggerHelper
builds a JVM args string like this:-agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=12345
, which links the gradle task with the debugger session IntelliJ has set up.Since Gretty tasks
appRunWar
, etc. don't implementJavaForkOptions
, it is impossible to get a debugging session without recurring to other tasks likeappRunWarDebug
and starting a remote debug session.It's great that we can start a remote debugging session, but I wonder if all
app*
tasks could implementJavaForkOptions
like other standard Gradle tasks. This would be very useful for people like me, that work with IntelliJ.The text was updated successfully, but these errors were encountered: