Major Description
While for resources, during a magma:run, it is possible to use magma.locals to have them automatically taken from their folder, and avoid rebuilding, no such a system is in place for java files. Moreover, LTW does not support debug class replacement.
If Eclipse was able to build packages correctly (including weaving etc..) then it would be enough to load classes from there, similarly to magma.locals, scan for changes and reload if necessary (which is already built in with jetty).
Since that is not the case yet, we could apply magma.locals to target/classes folders and scan those folders instead, so that rebuilding the target package could be enough. But still this method would require a different shell.
Monitoring .java class changes and triggering Maven compile could also be possible.