Simplify the API baseline target

[merks]

Also simplify the corresponding API baseline targlet in the setup

#39

[merks]

@jonahgraham @ruspl-afed

Guys, I submitted the changes as PR. Then I can see how the API baseline is used in the build and you can more easily review this in your local workspace...

[ruspl-afed]

I greet this change as it reduces support effort. Only one minor comment

[ruspl-afed]

Usually we have repository at the top and then we sort locations by repository::location

[merks]

I kind of doubt the test failures can be caused the API baseline change...

Now that I look closely, I don't think the baseline target is even used. The actual Maven build uses this which is out of date too:

		<comparator.repo>https://download.eclipse.org/tools/cdt/releases/10.6/cdt-10.6.0/</comparator.repo>

[merks]

Given the cdt-baseline.target is not used in the build, but rather is only used for a manual setup, reducing maintenance effort would definitely be a good thing...

[jonahgraham]

I kind of doubt the test failures can be caused the API baseline change...

Now that I look closely, I don't think the baseline target is even used. The actual Maven build uses this which is out of date too:

		<comparator.repo>https://download.eclipse.org/tools/cdt/releases/10.6/cdt-10.6.0/</comparator.repo>

That is the compare and replace repo. Separate from api baseline. As mentioned in the other comment I just made that eclipse-cdt/cdt-infra#59 needs to be done for next version and currently main hasn’t been prepped for post 10.7 yet.

BTW main branch will be 11.0 next, that is a major release of CDT is upcoming.

[jonahgraham]

I’m glad that you (Ed) are simplifying and that Alexander has time to review these changes. I will happily review anything left to review later.