[maven-scm-plugin] prepare release 1.4.1

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@530169 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
aheritier 2007-04-18 21:46:07 +00:00
parent 9403432827
commit 2b65f3c529
2 changed files with 61 additions and 56 deletions

View File

@ -1,4 +1,4 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
/*
@ -23,7 +23,7 @@
<pomVersion>3</pomVersion>
<id>maven-announcement-plugin</id>
<name>Maven Announcement Plugin</name>
<currentVersion>1.4.1-SNAPSHOT</currentVersion>
<currentVersion>1.4.1</currentVersion>
<description>The Announcement plugin generates release announcements. It uses the information found in both the POM and in the changes.xml file to generate the announcement text.</description>
<shortDescription>Produce release announcement</shortDescription>
<versions>
@ -52,6 +52,11 @@
<name>1.4</name>
<tag>MAVEN_ANNOUNCEMENT_1_4</tag>
</version>
<version>
<id>1.4.1</id>
<name>1.4.1</name>
<tag>maven-announcement-plugin-1.4.1</tag>
</version>
</versions>
<developers>
<developer>

View File

@ -18,100 +18,100 @@
* limitations under the License.
*/
-->
<document>
<properties>
<title>Announcement plugin changes</title>
<author email="vmassol@apache.org">Vincent Massol</author>
</properties>
<body>
<release version="1.4.1-SNAPSHOT" date="In SVN">
<action dev="aheritier" type="add">Add a link to the issue tracking system (if defined).</action>
<action dev="aheritier" type="update">Update dependencies to unify them between plugins. The following dependencies are updated : commons-net v1.4.0 to v1.4.1</action>
</release>
<release version="1.4" date="2005-12-12">
<document>
<properties>
<title>Announcement plugin changes</title>
<author email="vmassol@apache.org">Vincent Massol</author>
</properties>
<body>
<release version="1.4.1" date="2007-04-18">
<action dev="aheritier" type="add">Add a link to the issue tracking system (if defined).</action>
<action dev="aheritier" type="update">Update dependencies to unify them between plugins. The following dependencies are updated : commons-net v1.4.0 to v1.4.1</action>
</release>
<release version="1.4" date="2005-12-12">
<action dev="felipeal" type="add" issue="MPANNOUNCEMENT-19">Added property
<code>maven.announcement.lenient</code>.
</action>
</action>
<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-net v1.2.1 -&gt; v1.4.0</li>
<li>commons-jelly-tags-xml v1.0 -&gt; v1.1</li>
</ul>
</action>
<ul>
<li>commons-net v1.2.1 -&gt; v1.4.0</li>
<li>commons-jelly-tags-xml v1.0 -&gt; v1.1</li>
</ul>
</action>
<action dev="ltheussl" type="add" issue="MPANNOUNCEMENT-18">Support new format of
<code>&lt;action&gt;</code>element in
<code>changes.xml</code>.
</action>
<action dev="ltheussl" type="fix" issue="MPANNOUNCEMENT-3">CR-LF generated do not match the platform.</action>
<action dev="ltheussl" type="fix" issue="MPANNOUNCEMENT-10">Xml entities transformed in wrong direction.</action>
</action>
<action dev="ltheussl" type="fix" issue="MPANNOUNCEMENT-3">CR-LF generated do not match the platform.</action>
<action dev="ltheussl" type="fix" issue="MPANNOUNCEMENT-10">Xml entities transformed in wrong direction.</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-15">Modified the announcement text "
<code>The ${pom.groupId} team is pleased...</code>" in favor of "
<code>We are pleased...</code>" and changed the signature from "
<code>The ${pom.groupId} team</code>" to "
<code>The ${pom.name} development team</code>".
</action>
</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-16">Add information about the Maven remote repo to use in the generated download instructions. Added a
<code>maven.announcement.repo.remote</code>property that can be used to specify from which Maven remote repository the artifact for this project can be found.
</action>
</release>
<release version="1.3" date="2004-08-10">
</action>
</release>
<release version="1.3" date="2004-08-10">
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-14" due-to="Felipe Leme">Added check to verify that the POM has a
<code>version</code>element for the announcement to be generated.
</action>
</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-13" due-to="Felipe Leme">Added new optional
<code>maven.announcement.encoding</code>property that defines which charset encoding to use to generate the text announcement (defaults to UTF-8).
</action>
</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-9" due-to="Felipe Leme">Added new
<code>announcement:mail</code>goal to automatically send the generated announcement by email.
</action>
</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-11" due-to="Felipe Leme">Added new optional
<code>maven.announcement.stylesheet.path</code>property that defines what stylesheet to use to generate the text announcement.
</action>
</action>
<action dev="vmassol" type="fix" issue="MPANNOUNCEMENT-12" due-to="Felipe Leme">Fixed error message when current version is not available at
<code>xdocs/changes.xml</code>.
</action>
</release>
<release version="1.2" date="2004-07-08">
</action>
</release>
<release version="1.2" date="2004-07-08">
<action dev="vmassol" type="add">Added new
<code>announcement:generate-all</code>to generate announcement files for all releases.
</action>
</action>
<action dev="vmassol" type="update">Generates the announcement file in
<code>${maven.gen.docs}/announcements</code>so that it is copied to the web site when this later is deployed.
</action>
<action dev="vmassol" type="update">Default announcement file name now contains the version in its name.</action>
</release>
<release version="1.1" date="2004-05-15">
<action dev="brett" type="update">Detect whether the project is a plugin or not by the existence of plugin.jelly in the project directory, and change the wording accordingly.</action>
</action>
<action dev="vmassol" type="update">Default announcement file name now contains the version in its name.</action>
</release>
<release version="1.1" date="2004-05-15">
<action dev="brett" type="update">Detect whether the project is a plugin or not by the existence of plugin.jelly in the project directory, and change the wording accordingly.</action>
<action dev="vmassol" type="add">Added new
<code>maven.announcement.distributionUrl</code>property which specifies where the project jars can be downloaded from. If not specified, it defaults to
<code>${maven.repo.remote}/${pom.groupId}/plugins</code>. Once this property makes it into the POM we'll remove it.
</action>
</action>
<action dev="vmassol" type="update">The
<code>maven.announcement.version</code>property does no longer needs to be defined. It defaults to
<code>${pom.currentVersion}</code>if not defined.
</action>
<action dev="vmassol" type="add">Improved web site documentation.</action>
<action dev="vmassol" type="fix">Add a space after the "." of the "Issue: xxx." (which happens when you use the "issue" attribute in changes.xml).</action>
</action>
<action dev="vmassol" type="add">Improved web site documentation.</action>
<action dev="vmassol" type="fix">Add a space after the "." of the "Issue: xxx." (which happens when you use the "issue" attribute in changes.xml).</action>
<action dev="vmassol" type="add">Added
<code>description</code>information from the POM to the generated announcement to explain what the project does.
</action>
<action dev="vmassol" type="add">Added information in the generated announcement to indicate from where the plugin can be downloaded.</action>
</action>
<action dev="vmassol" type="add">Added information in the generated announcement to indicate from where the plugin can be downloaded.</action>
<action dev="vmassol" type="add">Added information in the generated announcement to indicate how to install the plugin using the
<code>plugin:download</code>goal.
</action>
<action dev="dion" type="update">Added maven.announcement.file property and echo'd it during generation</action>
</action>
<action dev="dion" type="update">Added maven.announcement.file property and echo'd it during generation</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-2" due-to="Fabrizio Giustina">Added more information when running the plugin. Also added a check to verify if the announcement version matches an entry in the
<code>changes.xml</code>file.
</action>
</action>
<action dev="vmassol" type="add" issue="MPANNOUNCEMENT-1" due-to="Fabrizio Giustina">Several new additions that makes the plugin more generic: the team name is now taken from
<code>pom.groupId</code>, "[]" are removed from the first line, changes are sorted by type, changes report issue number and due-to, the download link is generated from
<code>pom.distributionDirectory</code>and the "plugin has been tested with..." line has been removed.
</action>
</release>
<release version="1.0" date="2004-03-10">
<action dev="evenisse" type="update">Update to ASL v.2</action>
<action dev="jvanzyl" type="update">Remove the need for ${pom} interpolation in properties. The use of the maven:property tag is now used to glean a default property.</action>
<action dev="vmassol" type="add">Initial creation.</action>
</release>
</body>
</action>
</release>
<release version="1.0" date="2004-03-10">
<action dev="evenisse" type="update">Update to ASL v.2</action>
<action dev="jvanzyl" type="update">Remove the need for ${pom} interpolation in properties. The use of the maven:property tag is now used to glean a default property.</action>
<action dev="vmassol" type="add">Initial creation.</action>
</release>
</body>
</document>