Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt.dev] Fwd: [eclipse.org-planning-council] API Tools and Usage Scanning

Team,

If you are not already making use of the API Tooling, I strongly encourage you to do so. See below for information on how to enable it for your project.

Cheers,

Kenn

---------- Forwarded message ----------
From: Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx>
Date: Wed, Sep 2, 2009 at 4:19 PM
Subject: [eclipse.org-planning-council] API Tools and Usage Scanning
To: "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>


On the call today, I mentioned the requirement for people to use API Tooling. Here's a quick link on how to enable it:

It's as simple as running a wizard and selecting the projects you want to enable with API Tooling. It should take a minute.

As part of the Helios build, we should run the API Usage Scan provided by PDE. I ran a usage scan last year against some of the Galileo release and came up with this:

I can volunteer with Oisin to set this up for the Helios release. This is a service we can provide for people on the train. Plus, it should give us some insight in how people are using each other. We can plan fun games like who is the biggest abuser of internal code :)

Cheers,

--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.


Back to the top