JRebel plugin can't debug a grails project starting from IntelliJ IDEA 2017.3

ZeroTurnaround Homepage Forums JRebel Support JRebel plugin can't debug a grails project starting from IntelliJ IDEA 2017.3

This topic contains 2 replies, has 2 voices, and was last updated by  Hannes Metssalu 1 week ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #66870

    marcozim
    Member

    Any Grails (3.x) project opened in IntelliJ IDEA 2017.3 starts regurarly, but the ‘Debug with JRebel’ command behave exaclty like the ‘Run with JRebel’ one: no breakpoint is “checked” or hit during execution.

    I’ve tried the workaround suggested in https://zeroturnaround.com/forums/topic/jrebel-and-intellij-2017-3/, with no success.

    Any help would be appreciated.

    • This topic was modified 2 weeks ago by  marcozim.
    #66872

    Hannes Metssalu
    Rebel Staff

    Hi Marco,

    Thanks for letting us know. I looked into it and it seems that by default Grails is forking the actual application process. With the latest IntelliJ we fail to pass all the necessary arguments. I’ll let you know as soon as it’s fixed!

    Best,
    Hannes

    #66917

    Hannes Metssalu
    Rebel Staff

    Hey again,

    The issue should now be fixed, however it’s currently only available in our nightly build. Follow the instructions at https://zeroturnaround.com/software/jrebel/download/nightly-build/#!/intellij to try it out.

    All the best,
    Hannes

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.