On Wed, Nov 18, 2009 at 1:46 PM, David C. Hicks <[email protected]> wrote: > Of course...the build will break after a release because the new > changes.xml won't have a section for the new release version. > Come to think of it, will that even work? Since the CI sees a SNAPSHOT > version, and the changes.xml doesn't include SNAPSHOT.
Depending on which integration you use. Will work at least for jira, read the docs at http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html Kalle PS. Off-topic but make dependencies report go faster: <plugin> <artifactId>maven-project-info-reports-plugin</artifactId> <version>2.1</version> <configuration> <dependencyLocationsEnabled>false</dependencyLocationsEnabled> </configuration> </plugin> Maybe even dependencyDetailsEnabled to false if you so wish. > > David C. Hicks wrote: >> Good suggestion. I hadn't really thought of using CI to test the >> changes.xml. That's primarily because I also have the dependencies >> report generated as part of the Site generation. Under normal >> circumstances, it takes forever and a day to generate the dependencies >> report, since it appears to hit the Internet to find all the >> dependencies, instead of using the local repository. >> >> I suppose I can restructure my CI build to exclude the dependencies >> report and get some useful information about the changes report. >> >> Thanks! >> >> Kalle Korhonen wrote: >> >>> Changes plugin offers Jira and Trac integration. You can filter your >>> changes.xml if you cannot use current version only. Use ci system to >>> run the site and changes report so you know if it'll work or not >>> before the release. >>> >>> Kalle >>> >>> On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks <[email protected]> wrote: >>> >>> >>>> Hi folks, >>>> >>>> I'm using the Changes plugin to both produce a report for my Site and to >>>> distribute email announcements of changes. The problem is that if we're >>>> not careful to remember to update the changes.xml file itself, then our >>>> release build fails because it doesn't find a change set with the right >>>> version. I'd really like to find some way to automatically update the >>>> changes.xml file during the release build process. Can anyone recommend >>>> a plugin that might let me make modifications to this xml file at build >>>> time? Or, any other suggestions? >>>> >>>> Thanks, >>>> Dave >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
