On Wed, Dec 9, 2009 at 10:07 PM, Hakan Tandogan <[email protected]>wrote:
> Hi Brett, > > > Another little beautifying thingy :-) > > Would you mind if I changed the changes.txt file to the changes.xml format > as described in > http://maven.apache.org/plugins/maven-changes-plugin/changes.html ? > > I would do the conversion, and the result of the operation would be that > we can produce a nice changes report like the ones in most of the > mavenized projects: > > http://maven.apache.org/plugins/maven-changes-plugin/changes-report.html > > http://maven.apache.org/plugins/maven-changes-plugin/jira-report.html > > If needed, I can come up with some script to (re-) produce the changes.txt > file for the ivy build, but I'd really love to have those changes reports > :-) > Hmm, I'm not so sure about this one ... I'm concerned that once we go down this path we're stuck with maven to generate change reports. The idea of the text file was just a way to allow people to see what the key changes were in each release without having to trawl through subversion. If you could re-generate the changes.txt from within the ant build I'd be fine with it, but that sounds like a bit of work for you. I don't want to be a roadblock to improving things, but I don't want to impose additional overhead on those who build osmosis themselves. I guess if the whole build switched over to maven this wouldn't be an issue but I'm not sure I'm ready for that :-) I promise to test out your maven build one of these days ... Brett
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
