> -----Original Message----- > From: linuxtools-dev-boun...@eclipse.org > [mailto:linuxtools-dev-boun...@eclipse.org] On Behalf Of > Roland Grunberg > Sent: Friday, June 22, 2012 5:00 PM > To: Linux Tools developer discussions > Subject: [linuxtools-dev] Monitoring API Evolution > > Hi Everyone, > > Since we finally have a 1.0 release of our project, and given > that we'll be > graduating from Incubation, it will be important to monitor > changes to our > API. > > I've made a tutorial below demonstrating how I monitor API changes. Of > course committers could do this for just the individual > plug-ins that they > care about. > > http://rgrunber.wordpress.com/2012/06/22/setting-api-baselines > -in-eclipse/
The API tool is of great help and CDT is making heavy use of it. We used the same procedure as what you recommend until we realizzed that that procedure didn't allow for all errors to be shown (we don't know why). We updated the procedure to use an actual full installation and things work really well since then. Please see CDT's API tool setup instructions here: http://wiki.eclipse.org/CDT/policy#Using_API_Tooling and here is the email exchange that led us to update that procedure: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg23855.html BR, Marc > Cheers, and hope this helps. > -- > Roland Grunberg > _______________________________________________ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev > _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
