metHudson runs significant amount of code inside the Maven process for the native maven2 job type, and during the plugin development one would often like to debug this. Here's how you do it:
Debugging a maven job that runs on a slave works in a similar way. If port 5001 is already taken by Hudson's slave agent, then change the port to another value, e.g. 5002:
"-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=5002". Then connect your debugger to the IP address of your slave and the specified port (5001 or 5002).
CSET test - "Who Else Wants To 'Crack-The-Code' Of Your CSET Test In ONLY 7 Days And Go To $50,857.00 In California Teacher Salary Right Now...Much EASIER Than You Ever Thought Possible?"