I don't think it was ever a part of the Jenkins build process. I used to generate the diff locally on my machine by feeding the old and new version commands.xml files to the script.
We can generate this automatically using 2 ways: 1) Using @Since annotation for new parameters/commands. As a part of the build process, extract all the commands having @Since="current version" and put them into diff file. The annotation is already in place, but I believe most of the times people forget to update it for new commands/parameters they've been adding. 2) By keeping commands.xml of the previous version in the code base. As a part of the build process, generate the diff between version (n=current version) commands.xml and version (n-1). -Alena. On 4/5/13 9:31 AM, "Joe Brockmeier" <j...@zonker.net> wrote: >Bumping this. Any ideas? > >On Tue, Apr 2, 2013, at 03:33 PM, Joe Brockmeier wrote: >> Hi all, >> >> So - the build process for generating API docs has changed since 4.0 -> >> 4.1, and it looks like in the process we've stopped generating a >> "diff.txt" of APIs changed/added/deleted since the last version. >> >> Any idea how we can generate this automagically rather than combing >> through the new docs to see what's different since 4.0.x? Thanks! >> >> Best, >> >> jzb >> -- >> Joe Brockmeier >> j...@zonker.net >> Twitter: @jzb >> http://www.dissociatedpress.net/ > > >Best, > >jzb >-- >Joe Brockmeier >j...@zonker.net >Twitter: @jzb >http://www.dissociatedpress.net/ >
