![]() ![]() To find out, search for “rebel.xml” in jrebel.log. ![]() If you cannot find any monitored folders, it could mean that your rebel.xml is not present in the application archive or that it is incorrect. #Jrebel base manual#Refer to rebel.xml configuration in the reference manual for more information. If the monitored folders are present, you know exactly where JRebel is expecting to find updated classes and resources. If you do not find any, then probably rebel.xml has not been generated, or it is not present or recognized in the application archive. To do this, search jrebel.log for “monitored for changes”. Just changing some class does not cause it to be reloaded – unless you accessed it before.Īre the classes monitored? The first thing to check is that JRebel actually monitors the directories with compiled classes in your workspace. Note that JRebel only issues a console statement when a previous version of the class has already been loaded. Keep this in mind: when you are testing JRebel and think that classes are not being reloaded, be absolutely sure. Supported JVMs, IDEs, application servers and frameworks. #Jrebel base how to#How to configure JRebel logging from IDE?.I checked everything and it still does not work!.Make sure you are looking at the right console. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |