On 26 October 2013 10:07, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > > I recently came across Google Guice 4.0 Beta. They is a tool called JDiff > [1] to visualize API changes [2]. To me this report is much easier to > understand than the Clirr report. This is for the fact that it visualizes > the changes in an JavaDoc like format. When I think about an API, I always > think of it in terms of the packages and the classes, interfaces etc in > them. Clirr just produces an unstructured flat list. With JDiff I can > navigate to the packages I have in use and see exactly what has changes.
The JDiff report looks a lot more complicated to me (but I've not seen the Clirr Report for Guice) Also, as far as I can tell, JDiff does not classify whether the changes break compatibility. I suggest you create both reports in Lang and publish them via your people login so other developers can compare them. It may well be that both will be useful. > That said I'd like to propose to give JDiff a try in [lang]. There is a > maven plugin [3] but it is in beta state. Don't know if thats a no go for > us. > > Benedikt > > [1] http://www.jdiff.org > [2] > https://google-guice.googlecode.com/git/latest-api-diffs/4.0/changes.html > [3] http://mojo.codehaus.org/jdiff-maven-plugin/ > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
