On Mon, 2004-05-03 at 19:15, robert burrell donkin wrote: > On 2 May 2004, at 17:47, Henri Yandell wrote: > > > The only thing I can think of is the jdiff tool. As long as things are > > only added, I would assume binary compatibility is kept? > > > > So if jdiff were to create an xml report before the html [it might be > > able > > to do this], you could write something to create a different html > > report > > that merely cares about binary compatibility. > > there is a maven jdiff plugin which i've been using to create reports > on the difference between the betwixt refactoring branch and HEAD. it's > pretty easy to use so maybe that'd be worth trying...
jdiff is easy to use???? I think it's a nightmare to use. The documentation is almost incomprehensible. Maybe if you know Maven then using the maven plugin might be easier - I was running jdiff directly. In fact it's so horrible that I'm thinking of writing an alternative. A simple app which takes two jars and generates an xml report of the API differences between them (including listing binary incompatibilities) should not be too hard. However jdiff does (roughly) do the job once you get it working. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
