That JDiff tool I mentioned comes with an Ant Task, so can be automated. It has a LGPL 2.1 license.
I have no idea if that means that it would be possible to use it in the official release process in some way, or if the diffs would need to be created separately. On 29 July 2011 16:21, Sandro Martini <[email protected]> wrote: > Hi all, > some reference here ( > http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs ), for the theory > :-) . > > To have documentation on API evolution, I think it would be a great thing, > but has to be done by some automatic tool ... I've searched something for > Ant, a Maven (Report) Plugin, and other but I haven't found nothing at the > moment. > > But I remember that something automatic exist for this, I remember an > article (maybe on Java.net) to explain this feature for JTHarness or > something similar used by Sun, ... if I find something I'll post here an > update. > > If someone has other info/suggestions, are welcome. > > Bye, > Sandro > > > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/Suggestions-for-improving-the-Pivot-release-process-and-related-questions-tp3208415p3209094.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com. >
