It might require several rounds of configuration until JRebel get run but the result is so rewarded. Note that dont use **maven jetty:** run-war as Jrebel will watch changes on target/classes and it is not what we want. Therefore, in your IDE you must set on Build Automatically so that every change on source will be compiled to classes. Now all the changes on classes and webapp will be watched and redeployed. Then use mvn jetty:run and enjoy autoredeploy of JRebel.My MAVEN_OPTS as I extracted jrebel in C:/ In the environmental variables, set MAVEN_OPTS to have javaagent which points to the folder of jrebel.In the pom.xml, you need to set the maven jrebel plugin, i.e.**.
JREBEL LICENSE FREE HOW TO
Documents on how to run JRebel with Maven is a bit scarce however there is a few. I know most of dhis2 developers use Maven instead of IDE to build. Now steps to configure JRebel with dhis2.Follow the following tutorial to register the license (it is just a hashed string, you copy and paste into your license activation step).Don’t worry this posting is so rare, once a week or month. Going beyond what the company (ZeroTurnaround) advertises, JRebel is really rocks: Java code change effects immediately, so do *.vm, js, css super easy to getting start (please see my tutorial below) and its completely free if you join their social license, a license that integrates with Facebook so that JRebel can post few message on your behalf claiming how much time you can save using JRebel. I have tried JRebel and it is a big surprise to me. When a small change on java code must take few minutes for jvm to reload the context, coding becomes very arduous task, especially building portal with a large number of modules. One of the most time consuming task when programming with dhis2 is waiting for redeploying.
0 kommentar(er)
