Well I ended up using the 'Maven 2 Changes Plugin' to produce a changes-report based on the changes.xml that is input to the plugin.
I bind the plugin to the generate-resources phase, but found that it wouldn't allow me to override the outputDirectory, so the html report still ends up in the /site folder. I then use the antrun plugin to copy the file from the site directory to a new directory in webapp/pages/release (during the process-resources phase). So changes-report.html ends up getting embedded in the built WAR file. On 14/02/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote: > > > Seems like you have no other choice but to use the ant-run plugin just > for "replacing/filtering" part. > > Please see: > http://maven.apache.org/plugins/maven-antrun-plugin/introduction.html > > > > Pete wrote: > > >When I used to use Ant I had an ant target that would copy a pre-prepared > >HTML file into the webApp's pages - replacing/filtering ${build.date} ${ > >build.version} etc, so that Users and Testers could see which version of > the > >application they have deployed. > > > >I was about to do a similar function for Maven, but then wondered how > does > >everyone else do this ? > >Are there any M2 plugins to help ? > > > >I've seen the http://mojo.codehaus.org/changes-maven-plugin/howto.html > >'Maven 2 Changes Plugin', but presumably this is just published to the > >Application's Site, where as I want the information deployed as part of > the > >app's web pages. > > > >Any thoughts / suggestions appreciated. > > > >We're currently not using the release plugin because of the unresolved > >issues. > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
