maven-plugins/jboss/xdocs/changes.xml

96 lines
4.1 KiB
XML

<?xml version="1.0"?>
<document>
<properties>
<title>Changes</title>
<author email="vmassol@pivolis.com">Vincent Massol</author>
</properties>
<body>
<release version="1.4" date="in CVS">
<action dev="vmassol" type="fix" issue="MPJBOSS-3" due-to="Archimedes Trajano">
Fixed deploy/undeploy URLs for JBoss 3.2.
</action>
<action dev="vmassol" type="fix" issue="MPJBOSS-2" due-to="Sean Timm" due-to-email="stimm@proclarity.com">
Fix <code>jboss:shutdown</code> and <code>jboss:start</code> hanging on
pause.
</action>
</release>
<release version="1.3" date="2003-09-18">
<action dev="vmassol" type="fix" issue="MPJBOSS-1" due-to="Willie Vu" due-to-email="ctwillie@ust.hk">
Make the JBoss plugin work on unix (JBoss scripts have a sh extension
which we were missing).
</action>
</release>
<release version="1.2" date="2003-08-18">
<action dev="vmassol" type="fix" due-to="Willie Vu" due-to-email="ctwillie@ust.hk">
Fixed bug when using JBoss 3.0.4/Tomcat 4.1.12 is used. When
<code>jboss:start</code> is executed, it causes a
<code>NoClassDefFoundError</code>. This was due to the
working directory not being an absolute filename.
</action>
<action dev="dion" type="fix">
Copy dependencies using artifact path to allow jar overrides to work
</action>
<action dev="vmassol" type="add">
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>
<action dev="vmassol" type="fix">
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>
</release>
<release version="1.1" date="2003-06-17">
<action dev="vmassol" type="fix" due-to="Willie Vu" due-to-email="ctwillie@ust.hk">
Application-specific JBoss configuration files now correctly overwrite
the default JBoss configuration files.
</action>
<action dev="vmassol" type="update">
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>
<action dev="vmassol" type="add" due-to="James Johnson" due-to-email="jcej@tragus.org">
Added deploy/undeploy targets for jar/war/ear using JBoss' jmx console.
</action>
<action dev="vmassol" type="add" due-to="James Ward" due-to-email="james@ectropic.com">
Added new <code>maven.jboss.hostname</code> plugin property.
It defaults to <code>localhost</code> and gives the host name
of the server to stop when calling <code>maven jboss:stop</code>.
</action>
<action dev="vmassol" type="fix" due-to="James Ward" due-to-email="james@ectropic.com">
JBoss failed to start on unix. This has been fixed.
</action>
</release>
<release version="1.0" date="2003-04-08">
<action dev="vmassol" type="add">
Plugin creation.
</action>
</release>
</body>
</document>