I thought one of our primary use cases was generating API reports when api tools is NOT enabled on the plugin. I thought that was one of the main reasons I went through and debugged the api-tools ant tasks etc?

On 02/22/2013 02:36 PM, Mickael Istria wrote:
Hi everybody,

Soom we'll have API Tools part of the reports produced by build.
However, it seems to me that most (all?) JBoss Tools projects don't use API Tools. But it's not too late to start using them in your IDE, in a long-term view, it's very useful and can prevent from some serious bugs and will help you to choose the best version to put for your dependencies in your MANIFEST. Here is a reminder of how to set them up: http://eclipsesource.com/blogs/2013/02/21/api-tools-revisited/ . In our case, the "baseline" is the latest release of JBoss Tools or JBoss Developer Studio.

Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev