|
Hi Michael,
I'm travelling at the moment so I'll comment in more depth in a
couple of days. This sounds great.
Thank you,
Andrew
On 02/27/2013 01:37 PM, Mickael Istria wrote:
Hi all,
Since we'd like to have some API Tools for JBoss Tools, but we're
trying to avoid any eclipserun or antrunner plugin to do this job
because they make the build more difficult to maintain, we've
worked on Mojo that does what we need of API Tools. We've already
described our efforts here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=399276
Here is the latest version of this mojo and dependencies: https://github.com/mickaelistria/apitooling
You'll see on the documentation how to give it a try without
requiring to build anything (we have some experimental Nexus repo
that contain everything necessary). There are currently 2 goals:
* one to generate .api_description file on eclipse-plugin
* one to generate api reports on an eclipse-plugin or an
eclipse-repository that compares bundles with a baseline.
That is something we'd like to contribute to Tycho and CBI when
it's good enough. But before that, we'd like to collect some
feedback. So if you have time to give it a try, please do it, and
give us feedback. This can be answers to this mail, GitHub issues
or pull requests.
You'll notice that the Mojo has some Eclipse bundles as
dependencies, that needs to be available in a Maven repositories.
We just put them in one of our repo using a "mvn deploy-file".
That also raise the question of whether the artifacts built by CBI
should go into a Nexus repository for wider-consumption (by wider
I mean out of Eclipse, in a Maven mojo, in a webapp, in an Android
app...)
Cheers,
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
|
