Today jooby:run is able to reload an application while working in development. This feature increase developer productivity and provides a nice development experience.
But jooby:run isn't able to recompile classes on file changes so it must be used it with other tools... the perfect combo is: jooby:run + Eclipse IDE. Because, Eclipse recompile code on Save and jooby:run is able to reload the application.
Next release of the jooby:run maven plugin will come with a live compiler. The compiler is on by default, unless:
- A
.classpath file is detected at the project dir. If this file is present, then developer uses Eclipse and the plugin will let Eclipse do his job (as today)
- The compiler option is set to
off
- Otherwise the live compiler is always
on
On compilation success, the application will be effectively reloaded.
On compilation error, the application will ignore the change and won't reload.
Compilation error or success are display at the console (not at the browser)
Today
jooby:runis able to reload an application while working in development. This feature increase developer productivity and provides a nice development experience.But
jooby:runisn't able to recompile classes on file changes so it must be used it with other tools... the perfect combo is:jooby:run+Eclipse IDE. Because, Eclipse recompile code onSaveandjooby:runis able to reload the application.Next release of the
jooby:runmaven plugin will come with alive compiler. Thecompilerisonby default, unless:.classpathfile is detected at the project dir. If this file is present, then developer usesEclipseand the plugin will letEclipsedo his job (as today)offonOn compilation success, the application will be effectively reloaded.
On compilation error, the application will ignore the change and won't reload.
Compilation error or success are display at the console (not at the browser)