Re: [m2e-dev] semantic versioning / Re: Starting a 2.0 with breaking cha

[Mickael Istria <mistria@xxxxxxxxxx>]

On Thursday, February 17, 2022, Hannes Wellmann <wellmann.hannes1@xxxxxxx> wrote:
> Using API Tools like it is done for the Eclipse Platform project builds at the moment seems to be cumbersome.

I don't buy that PDE API Tools are too complex to set up, and don't believe it's the reason why so few projects do use them:

* In the IDE, it's a few clicks to enable and setup a baseline in preferences

* In Maven/Tycho, it's one (sure, 219 lines) profile to copy-paste: https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse-platform-parent/pom.xml#L730..L949 . While a more compact solution for Maven would be nice, we can't really say that copy-pasting 1 profile is really cumbersome and that those steps are too difficult to perform to be the main reason for not using API Tools.

If you want to start using PDE API Tools in m2e, it's probably about 2 hours of work to tweak the parent pom and the .project files so it's enabled, and most of that time time would be actually waiting to verify some build output.

I'm not really advocating PDE API Tools over BND baselining here, I just want to make sure that we identify the right pros and cons of each if we want to pick one, or both; so I just reject the argument that the setup is a major difficulty for PDE API Tools.

Cheers,