IDE Setup
There are two setups for your IDE to get the most out of using devcat server.
Remote Debugging
Devcat uses the Java Platform Debugging Agent (JPDA) to open a remote debugging port using the following options by default
jdwp=transport=dt_socket,address=*:54455,server=y,suspend=n
Use a “JVM Remote Debugging” debug configuration in your IDE with the above options to connect your IDE debugger to the running devcat server.
Auto Build
The hotswap-agent watches the classes and jars that are loaded by the webapps. This is especially useful for the extra-class-path that is usually defined by the –source-dir option.
By this devcat collects recursively all target/classes folders in the given <soruce-dir> folder.
Thus, running the Maven build will update the class files in the target/classesfolders and the hotswap-agent is immediately picking them up and redefines the classes on the fly in the running devcat server.
Finally, the most streamlined reload experience will be achieved by building the class files immediately by your favorite IDE after changing code.
See docs e.g. for