Vincent Massol Fixed deploy/undeploy URLs for JBoss 3.2. Fix jboss:shutdown and jboss:start hanging on pause. Make the JBoss plugin work on unix (JBoss scripts have a sh extension which we were missing). Fixed bug when using JBoss 3.0.4/Tomcat 4.1.12 is used. When jboss:start is executed, it causes a NoClassDefFoundError. This was due to the working directory not being an absolute filename. Copy dependencies using artifact path to allow jar overrides to work The plugin now supports JBoss 3.2.x by default. Support for JBoss 3.0.x is still available by setting the maven.jboss.version=3.0 property. Added default start/stop script that are packaged into the generated jboss zip. Custom scripts can also be provided by overriding the maven.jboss.script.dir property. When generating the JBoss server configuration zip, exclude JBoss tmp and log directories from the zip. Change strategy for bunding J2EE modules in the jboss server configuration. This is now achieved through dependencies in project.xml. for any J2EE module you want to incude add a jboss.bundle property in the said dependency definition. Application-specific JBoss configuration files now correctly overwrite the default JBoss configuration files. Allowed deployments of EAR, WAR or EJB-JAR (only EAR was previously supported) by adding the jboss:package-ear, jboss:package-ejb and jboss:package-war goals. The jboss:package goal has been renamed jboss:configure and now simply creates a custom JBoss server configuration (with nothing from the project deployed in it). Added deploy/undeploy targets for jar/war/ear using JBoss' jmx console. Added new maven.jboss.hostname plugin property. It defaults to localhost and gives the host name of the server to stop when calling maven jboss:stop. JBoss failed to start on unix. This has been fixed. Plugin creation.