You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Benedikt Ritter <br...@apache.org> on 2013/10/26 11:07:47 UTC
[LANG] Use JDiff instead of Clirr?
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.
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
Re: [LANG] Use JDiff instead of Clirr?
Posted by Gary Gregory <ga...@gmail.com>.
If I had to pick between JDiff and Clirr, I'd pick Clirr. Not to say there
is no value in JDiff, there is, but Clirr serves our purpose better IMO,
because Clirr tells me when I've broken compatibility. I see the value in
JDiff in organizing the information in a different way. I could see that
have both might help some users in some cases. Which begs the question, why
not better integrate JDiff/Clirr information in Javadoc itself, a topic for
a different thread and a different tool ;)
Gary
On Sat, Oct 26, 2013 at 7:44 AM, sebb <se...@gmail.com> wrote:
> On 26 October 2013 10:07, Benedikt Ritter <br...@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [LANG] Use JDiff instead of Clirr?
Posted by sebb <se...@gmail.com>.
On 26 October 2013 10:07, Benedikt Ritter <br...@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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org