We are looking into an automated way to get a changelog of all our libraries between releases. Clearly, the maven-changelog-plugin is great for that on an individual project (perhaps coupled with maven-changes-plugin, if only it supported a Bugzilla report...).
Has there ever been any talk of deploying the changelog as a separate artifact so that a dependent project can include those changes in its own changelog? Our company has many internal libraries that are shared across many projects (hence most are not multi-module monoliths where a single changelog is possible). For our purposes, we would likely only want to have a changelog of our internal dependencies (easy to filter based on groupId). Would anyone else be interested in such a feature, if we were to implement it either as a submission to the maven-changelog-plugin or as a separate plugin? The trick, of course, is keeping track of what dependency versions have changed, and handling that multiple versions of a library may have been released in between a release of the top-level project. I imagine getting the previous release pom from Nexus, parsing the dependency versions, and then fetching all the changelogs for those intermediate versions. I suspect most projects do this sort of thing by using the maven-changes-plugin and each bug being cross-listed, if it affects multiple projects. And new features are also listed as issues, which are completed in a version as well. So perhaps that is the direction we should head, but I thought I would ask about changelog's too. -Ben -- Ben Tatham Software Developer Nanometrics Inc. +1 613-592-6776 x254 http://www.nanometrics.ca
