maven-plugins/ejb/xdocs/changes.xml
aheritier 4eee931710 Use recent releases of dependencies to allow developers to use them in plugins :
* commons-logging v1.0.3 -> v1.0.4
* log4j v1.2.8 -> v1.2.12

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@321081 13f79535-47bb-0310-9956-ffa450edef68
2005-10-14 12:00:34 +00:00

95 lines
5.5 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<!--
/*
* Copyright 2001-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-->
<document>
<properties>
<title>Changes</title>
<author email="nathan.coast@blueyonder.co.uk">Nathan Coast</author>
<author email="vmassol@apache.org">Vincent Massol</author>
</properties>
<body>
<release version="1.8-SNAPSHOT" date="in SVN">
<action dev="aheritier" type="update" issue="MAVEN-1712">Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated :
<ul>
<li>commons-logging v1.0.3 -> v1.0.4</li>
<li>maven v1.0 -> v1.0.2</li>
<li>maven-model v3.0.0 -> v3.0.1</li>
</ul>
</action>
</release>
<release version="1.7.1" date="2005-08-28">
<action dev="brett" type="fix">Update dependency to Maven Model v3.0.0 final (it was previously depending on 3.0.0 SNAPSHOT).</action>
</release>
<release version="1.7" date="2005-08-27">
<action dev="vmassol" type="update">By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common.</action>
<action dev="vmassol" type="fix">Make the ejb creation work even if there are not sources.</action>
<action dev="vmassol" type="fix" issue="MPEJB-12">Fixed default property values in the web site documentation.</action>
<action dev="vmassol" type="fix" issue="MPEJB-2">EJB client jar can now be generated and deployed/installed automatically by the standard goals (
<code>ejb</code>,
<code>ejb:ejb</code>,
<code>ejb:install</code>and
<code>ejb:deploy</code>). Previous goals dedicated to ejb client have been deprecated. There is a new property
<code>maven.ejb.client.generate</code>which decides whether or not to generate the ejb client jar. It defaults to true.
</action>
<action dev="vmassol" type="fix" issue="MPEJB-16" due-to="H�vard Bj�stad">Added new EJB type handler that supports
<code>ejb</code>and
<code>ejb-client</code>types. This fixes the bug with
<code>ejb:install/deploy-client</code>not uploading the client jar.
</action>
</release>
<release version="1.6" date="2005-05-01">
<action dev="vmassol" type="add">Added new
<code>maven.ejb.build.dir</code>property that specifies the location where the EJBs are generated.
</action>
<action dev="vmassol" type="update">Modified existing
<code>maven.ejb.final.name</code>property (and exposed it as a public property) so that it doesn't include the path (the path is now provided by the new
<code>maven.ejb.build.dir</code>property). This allows aligning the WAR and EJB plugin properties. Note: This is a breaking change for all those using the
<code>maven.ejb.final.name</code>property (which was not a public property).
</action>
<action dev="vmassol" type="update">Made the
<code>maven.ejb.final.name</code>property public as it is required by several other plugins and before this change the only way is for these plugins was to call the non-public
<code>ejb:init</code>goal.
</action>
</release>
<release version="1.5" date="2004-07-09">
<action dev="evenisse" type="fix" due-to="Martin van den Bemt" issue="MPJAR-29">Replace Apache Jakarta Maven by Apache Maven in Manifest</action>
<action dev="evenisse" type="add">Add ejb:install-client and ejb:deploy-client goals.</action>
</release>
<release version="1.4" date="2004-05-15">
<action dev="dion" type="fix">Don't generate a Class-Path manfiest entry if there are no jars with ejb.manifest.classpath set to true</action>
</release>
<release version="1.3" date="2004-01-29">
<action dev="dion" type="fix">Only include maven.ejb.src if it exists</action>
</release>
<release version="1.2" date="2003-11-26">
<action dev="dion" type="fix" issue="MAVEN-936">Synchronize ejb and jar plugin usage of: Specification-Title/Vendor/Version and Implementation-Title/Vendor/Version</action>
</release>
<release version="1.1" date="2003-09-29">
<action dev="evenisse" type="add">Added maven.ejb.index, maven.ejb.client.index properties.</action>
<action dev="evenisse" type="add">Added maven.ejb.excludes and maven.ejb.includes properties.</action>
<action dev="michal" type="add">Added deploy, deploy-snapshot and install-snapshot goals</action>
<action dev="michal" type="fix" issue="MAVEN-518">Artifact processing in the plugin was slightly changed and now it supports jar overriding mechanism</action>
<action dev="michal" type="fix">property ejb.bundle.jar was renamed to ejb.bundle (old property is still supported, but deprecated)</action>
</release>
<release version="1.0" date="2002-08-04">
<action dev="ncoast" type="add">Initial plugin created</action>
</release>
</body>
</document>