> 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 wor
> -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 Evolu
> It has the 1.0 p2 repo URL in it in
> plain text and we're not really supposed to publish that until
> release
> day.
>
> Sorry to be (like in your blog entry) the "don't release until the
> release day" police :)
I've replaced it with just a place holder for some repo.
Cheers,
--
Roland Grun
> http://rgrunber.wordpress.com/2012/06/22/setting-api-baselines-in-eclipse/
This is great stuff, Roland! Do you think you could wait until
Wednesday to publish it, though? It has the 1.0 p2 repo URL in it in
plain text and we're not really supposed to publish that until release
day.
Sorry to b
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 p
