See also the main changes related to all plugins.

pluginInfo 0.2

This plugin provides various mechanisms for extracting and displaying information about one or more projects.

Use @context and @version to create unique section identifiers in the list of changes. Fix URLs to issues in the release notes generation. Adding svn support specific properties to the default.plugin.properties.xml. Further activated this new properties (projectInfo.svn.ext and projectInfo.svn.path-prefix) in the svn-log.xsl. This allows to have a more flexible export string. Add support for svn log files. This let you extract changes based on a svn log file. Further this provides some handy ways to find out the first and last commit of a month and the generation of svn cli commands. Enable optional release/introduction elements. Allow an aggregation of all use cases in a project. Start off a use case document for the changelog features of the plugin. Add section to output "Introduction and explanation of symbols". Show the unique symbols. List all contributors for each release by showing a list of committers and a list of other contributors. Fixing small issue with the last ',' which should not be displayed on the last entry of the contributors list. Using a unique key including the release version. Make the list of contributors for each release be a compact list. Changed rendered text for @dev attribute from "(@dev)" to the more explicit "Committed by @dev.". Changed rendered text for @fix-for from "Fixes" to the more general "See Issue". Add support for Use Case documentation. This can be used to generate various different types of user an developer documentation, such as step by step user instructions, or developer implementation notes. See http://localhost:8888/docs/developer/useCases.html for more information. Use locationmap for resolution of resources and files. Resources are exposed via {lm:projectInfo.*} do not limit status.xml contexts in projectinfo plugin. Added RSS changes feeds for individual versions. Removed todo items from changes RSS feed. Add configuration options to control sorting of changes and inclusion of developer and committer lists. Add list of committers and developers to changes document. Enable project-level locationmap to define the location of the project:status file which contains the change notes. Therefore this can even be from a remote location. Add an automated index page that lists all projects in a category. Use projectDetails/category/*.xml to retrieve it. Add an automated project index page that lists all projects grouped by Category. Use projectDetails/category-index.xml to retrieve it. Add an automated index page that lists all projects using a specific language. Use projectDetails/*-lang.xml to retrieve it. Add an automated project index page that lists all projects grouped by language. Use projectDetails/lang-index.xml to retrieve it. Add an automated index page for all projects using a specified programming language. Use projectDetails/*-lang.xml to retrieve it. Add an automated site.xml snippet that provides links to an index page for all languages in use in all projects. XInclude projectDetails/lang_index.siteSnippet.xml in your site.xml file. Add an indexing capability for all known project descriptors. Use locationmap to expose plugin resources. Add projectDetails page using the DOAP.xml descriptor.
PluginInfo 0.1

This plugin encapsulates and extends functionality that was originally in Forrest Core. With the advent of plugins in Forrest 0.7 we extracted the functionality for generating changes.xml and todo.xml from the status.xml file. It is intended that this functionality be extended further within this plugin.

In fact, we have already extended the functionality in a couple of important ways. See the changelog for more details.

Add projectDetails page using the DOAP.xml descriptor. Use the value "current" for the releaseNotes_* URI or specify a version number, i.e. show what is new for the latest release. Basic documentation on how to create release notes are now included on the plugins documentation index page. Added automatic generation of release notes by requesting **/releaseNotes_VERSION-NUMBER.xml Added optional "notes" element to "release" element of status 1.3 DTD. This will be inserted into the release notes for that version. Enable the generation of changes for a specific version by requesting **/changes_VERSION-NUMBER.xml Use relative location of images directory. Added better sitemap match using regexp to deal with sub-directories too. Replace use of document() function in changes2rss.xml with sitemap aggregation. Use the "title" attribute of "changes" and "todo" tags if it exists, otherwise use the hard-coded values. Move ToDo and Changes pipelines to this plugin, from core. Initial plugin code. Add an attribute to the action element in skinconfig called "announce" with a value of true or false (default to false), and auto generate the announcement of new features. Add an element "upgrade" which contains a textual description of what actions this change require in order to upgrade from the previous version and use this to generate the upgrade document. Create an icon for and action of type "refactor". Move DTD's to this plugin from core (depends on having a catalog extension mechanism for plugins). Look at the make sourcetype actions for changes in sitemap.xmap and either remove them or bring them here as appropriate. Move images from core to this plugin.