#! /bin/sh
# ----------------------------------------------------------------------------
# Default JBoss start up shell script in debug modes. It calls the default script found
# in JBOSS_HOME/bin.
# ----------------------------------------------------------------------------
export JAVA_OPTS="-Djboss.server.home.dir=@jboss.server.home.dir@ -Djboss.server.home.url=@jboss.server.home.url@ -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=@jboss.server.debug.port@,suspend=n"

#Xrunjdwp... == the info on how to connect to do remote debugging 
#server=y == start in server mode (i.e. wait for connections, don't go out looking to connect 
#transport=dt_socked == use sockets, this works (I think) only on unix (I'm on a mac), on Windows you have to use shared memory via the transport=dt_shmem argument instead. I'm fairly sure this works but its been a while since I tried it on Windows. YMMV. here is the official info on the connection arguments 
#address=4142 == the port to connect to or the shared mem address to use 
#suspend=n == don't wait for a debugger to tell you what to do, go ahead and launch 

@maven.jboss.home@/bin/run.sh -c @maven.jboss.conf.name@