This method uses a Maven plugin called Wagon to upload and execute/debug a jar on another machine. IntelliJ supports executing any kind of scripts or programs during a remote deploy beyond Maven commands, so you may find those easier to create and use.
Install an SSH server on your remote box.
- sudo apt-get install openssh-server
- sudo vim /etc/ssh/sshd_config
- sudo /etc/init.d/ssh restart
Add a <server> block to settings.xml in .m2 folder on the box with the code:
Your project’s pom.xml additions:
Replace [ip.address] with your remote box’s ip. Replace the <fromDir> with your project’s target directory. Replace the <includes> with the jar or file patterns that you wish to deploy.
Place a startup script ‘start.sh’ in the root SSH directory of your remote box:
Replace the classpath with the root scp folder and your project’s jar artifact. Replace the TestCron class with your main class. Replace 4001 with your desired debugging port (open this port in your remote box firewall). Use suspend=n if you don’t want to wait for the debugger. Replace log.txt with what you want to catch stdin and stderror.
java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=4001 -cp “C:\Program Files (x86)\ICW\testcron-1.0-SNAPSHOT.jar” com.test.TestCron > log.txt 2>&1 &
You can also put the start.sh command(s) in the pom.xml file in the <commands> section. I had issues with the ampersands in xml, so I created a script to execute instead.
Create a new Run/Debug Configuration in IntelliJ on your code box with the following params and Maven goals:
Host: 192.168.1.10 (your remote box’s ip)
Port: 4001 (The debug port from the start.sh script)
Click ‘Debug’ and your jar will be built, scp’d to your remote box, executed with an ssh exec of your start.sh script, and the IntellIJ debugger will connect. Debug as normal and tail log.txt for output, or whatever file log4j is set to. Package any property files into the jar or place them in the root scp folder for the jar to use.