The plugin now supports JBoss 3.2.x by default. Support for
JBoss 3.0.x is still available by setting the
<code>maven.jboss.version=3.0</code> property.
</action>
<action dev="vmassol" type="add">
Added default start/stop script that are packaged into the
generated jboss zip. Custom scripts can also be provided by
overriding the <code>maven.jboss.script.dir</code> property.
</action>
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113527 13f79535-47bb-0310-9956-ffa450edef68
When generating the JBoss server configuration zip, exclude
JBoss tmp and log directories from the zip.
</action>
<action dev="vmassol" type="update">
Change strategy for bunding J2EE modules in the jboss server
configuration. This is now achieved through dependencies in
<code>project.xml</code>. for any J2EE module you want to incude
add a <code>jboss.bundle</code> property in the said dependency
definition.
</action>
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113522 13f79535-47bb-0310-9956-ffa450edef68
Allowed deployments of EAR, WAR or EJB-JAR (only EAR was previously
supported) by adding the <code>jboss:package-ear</code>,
<code>jboss:package-ejb</code> and <code>jboss:package-war</code>
goals. The <code>jboss:package</code> goal has been renamed
<code>jboss:configure</code> and now simply creates a
custom JBoss server configuration (with nothing from the project
deployed in it).
</action>
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113347 13f79535-47bb-0310-9956-ffa450edef68
o Bumping all plugin version to release status
o Validated all plugins to make sure all snapshots were removed.
I had to manually insert the versions for:
1) ashkelon
2) commons-dbcp
Not sure how either of these got up there without the timestamp
mapping.
PR:
Obtained from:
Submitted by:
Reviewed by:
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@113303 13f79535-47bb-0310-9956-ffa450edef68
