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

[Hannes Wellmann <wellmann.hannes1@xxxxxxx>]

My intention was not to say it is too complex to set up, but as Christoph said, it's complex.

Therefore it would indeed be nice to have a simpler solution, ideally a single plug-in where you configure everything necessary (the path to the baseline repo (ideally p2?) and I think that's it).

It should be as simple as for example setting up source generation for Eclipse Plugins/Features in Tycho.

 

Originally I thought a good start would be a plug-in that does what's now done in the mentioned profile, when that works maybe it would be possible to improve the runtime subsequently.

But in case an approach based on the BND-baseline plugin suggestion works better with less effort and also integrates well with the IDE, I would have no objections, as long as it can work with p2 repos.

 

Gesendet: Freitag, 18. Februar 2022 um 07:02 Uhr
Von: "Christoph Läubrich" <laeubi@xxxxxxxxxxxxxx>
An: m2e-dev@xxxxxxxxxxx
Betreff: Re: [m2e-dev] semantic versioning / Re: Starting a 2.0 with breaking changes soon?

Just from a users perspective, if I need to find an example pom and copy
large parts from it, I would qualify this as "complex".

I also always get annoyed by API tool when develop Platform code because
it either gives me false positives the build does *not* complain, does
not give me errors the build complains, or I had to perform lengthy
setup tasks to get the 'right' baseline.

Anyways this might be possible to getting more smooth or its just my
inability to understand that API baselining :-)

What I have in mind should more be setup in 5 minutes than 2 hrs...

Am 18.02.22 um 06:37 schrieb Mickael Istria:
>
>
> On Thursday, February 17, 2022, Hannes Wellmann
> <wellmann.hannes1@xxxxxxx <mailto: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
> <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,
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev