THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Fire when change made to CVS; but don't fire too often.
- Generate and deploy new website for developers, containing many Maven reports (some mentioned in later bullets).
- Update the build.xml via maven each time project.xml is changed, or project.properties?
- Update the gump descriptors each time a project.xml is changed.
- Update a wrapping interface that allows cross-referencing of many of the Maven reports.
- Generate a jdiff report against the last released version.
- Use rsync rather than maven site:deploy to save on bandwidth.
- Should apply to sandbox'd items too; though should separate sandbox and components.
- A top-level report showing the dependencies between various components.
I'd like the wrapping interface for the release site too. This would probably be updated nightly and then rsync'd.
Steps?unmigrated-wiki-markup
Obviously I'm (HenriYandell) tied to my own tools and need kicking to use something else. I'd use an improved variant of \[http://builds.osjava.org Integration\] for the automated developer site and \[http://multidoc.osjava.org Multidoc\] as the wrapping-interface.