JRebel – IntelliJ – Gradle – certain java classes will not hot-deploy

Forum on this website is being phased out. New threads or replies cannot be posted. Existing content remains available for now in read only mode. You can contact technical support at support@zeroturnaround.com.

ZeroTurnaround Homepage Forums JRebel Support JRebel – IntelliJ – Gradle – certain java classes will not hot-deploy

This topic contains 1 reply, has 1 voice, and was last updated by  Nicholas DiPiazza 1 month, 4 weeks ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #67043

    I am using JRebel + Intellij JRebel IDE Plugin to hot deploy a gradle project.

    I have a situation with JRebel where there are certain Java classes that JRebel refuses to allow me to hot-deploy.

    Some classes reload fine.

    Other classes do not reload at all. (often in the same gradle sub-project as classes that reload OK)

    There is no rhyme or reason to why they do not want to reload.

    It is making JRebel pretty much unusable.

    I created a custom JRebel plugin for our project hoping it would help but it did not. Because the class itself will not trigger a reload event, the plugin fails to help fix this.

    Note the class in question that will not reload is often an implementation of an interface where if I change the implementation, no reload happens. But if I change the interface java class, that will reload fine!

    There is something that JRebel in particular does not like about the Java class files.

    When I build the files that it won’t pick up, you can even see in the IDE and 100% of the time for these files I get a 0 classes reloaded message on my debug session:

    can't reload


    Note: We use Guice… but I don’t think that is necessarily why this is happening.

    I have a file that fails to reload that isn’t a guice managed class as well.

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

The forum ‘JRebel Support’ is closed to new topics and replies.