Vincent Massol Added new announcement:generate-allto generate announcement files for all releases. Generates the announcement file in ${maven.gen.docs}/announcementsso that it is copied to the web site when this later is deployed. Default announcement file name now contains the version in its name. Detect whether the project is a plugin or not by the existence of plugin.jelly in the project directory, and change the wording accordingly. Added new maven.announcement.distributionUrlproperty which specifies where the project jars can be downloaded from. If not specified, it defaults to ${maven.repo.remote}/${pom.groupId}/plugins. Once this property makes it into the POM we'll remove it. The maven.announcement.versionproperty does no longer needs to be defined. It defaults to ${pom.currentVersion}if not defined. Improved web site documentation. Add a space after the "." of the "Issue: xxx." (which happens when you use the "issue" attribute in changes.xml). Added descriptioninformation from the POM to the generated announcement to explain what the project does. Added information in the generated announcement to indicate from where the plugin can be downloaded. Added information in the generated announcement to indicate how to install the plugin using the plugin:downloadgoal. Added maven.announcement.file property and echo'd it during generation Added more information when running the plugin. Also added a check to verify if the announcement version matches an entry in the changes.xmlfile. Several new additions that makes the plugin more generic: the team name is now taken from pom.groupId, "[]" are removed from the first line, changes are sorted by type, changes report issue number and due-to, the download link is generated from pom.distributionDirectoryand the "plugin has been tested with..." line has been removed. Update to ASL v.2 Remove the need for ${pom} interpolation in properties. The use of the maven:property tag is now used to glean a default property. Initial creation.