[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tycho-dev] tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines
- From: LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx>
- Date: Wed, 28 Oct 2015 15:25:16 +0000
- Accept-language: fr-FR, en-US
- Delivered-to: email@example.com
- Thread-index: AQHREZPX1UOxkJg5X0GEsQiBOtyDD56BBmLg
- Thread-topic: [tycho-dev] tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines
Thanks for the links
I will study it closely.
Francois from France
De : tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] De la part de Matthias Sohn
EnvoyÃ : mercredi 28 octobre 2015 16:18
Ã : Tycho developers list <tycho-dev@xxxxxxxxxxx>
Objet : Re: [tycho-dev] tycho-p2-extras-plugin:0.24.0:compare-version-with-baselines
On Wed, Oct 28, 2015 at 10:44 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
On 10/28/2015 09:54 AM, LE FEVRE FRANCOIS wrote:
But I was expected to have like a report as output?
How can I see my plugin do not break the API?
As explained in https://wiki.eclipse.org/Tycho/Release_Notes/0.24#compare-version-with-baselines_mojo and in the Mojo documentation (that will be available in tycho documentation site when 0.24 is released), the compare-version-with-baseline mojo is purely about checking the version. It does not dig into APIs.
If you're interested into API checking with Tycho, you can have a look at this (more or less abandonned) experiment: https://github.com/mickaelistria/apitooling/ . I tried to get some more people playing with it and helping in integrating it to CBI in the past, but didn't manage to find people interested enough in it. And for JBoss Tools, although it would be nice to have, it appeared that automatic check of API versions at build-time didn't appear as a big issue compared to the difficulty of automating the checks.
If you want to revive this project and ultimately make it part of tycho-extras or CBI, I'd be glad to help you.
On this API versioning topic, I believe the CLIRR and/or BND have some working solutions, that might be preferred to the work mentioned above.
for JGit we recently moved  from Clirr to japicmp  sincle Clirr doesn't support Java 8
If it does not exist (perhaps there is an hidden option not documented in the web site?) , will you add a maven html report?
I consider that HTML reports are the worst way to report such issues (who reads reports?). The current strategy for the compare-version-with-baselines mojo is to fail the build if version seems illegal.
We generate a html API report  using japicmp when generating the jgit maven site, you can configure
japicmp to break the build on breaking changes (see e.g. ).
Description: S/MIME cryptographic signature