Announcement plugin changes
Vincent Massol
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.distributionUrl property
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.version property 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 description information 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:download goal.
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.xml file.
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.distributionDirectory
and 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.