platform-config | Layered configuration for rust cli apps

I have created an eclipse plugin, with the following Manifest file:

In my tycho test project, I have an optional transitive dependency that I need to exclude for the test execution to work. That transitive dependency is part of the same reactor build.

What I have tried:

I am working on integrating some google maps functionality into a Xamarin Forms project, since I haven't found some decent videos on the topic I am using some Microsoft Documentation as a reference for my code. Right now I am trying to display a new Map but I am showed with only a gray box, I know this is caused by the API key not working and the following message in the debug output.

Here's how I have set up my API key in the Android manifest, I followed the Google documentation

I have a build for a single-sourced RCP/RAP Eclipse feature project that uses maven profiles to either build RAP or RCP bundles, fragments and features.

This works reasonably well. If I include my update site project as module in the above build's parent POM I can also easily build a platform-specific update-site using either "eclipse-update-site" (or "eclipse-repository") packaging.

However, I was wondering, if there is a way to

1. build RCP target platform > publish to local repo
2. build RAP target platform > publish to local repo
3. run build for RCP (target platform from step 1) > publish to local repo
4. run build for RAP (target platform from step 2) > publish to local repo
5. run build for update site only, include feature for RAP and for RCP (not compiling anything, just assembling from 1+2)

I could successfully execute steps 1-4, but not 5, because Tycho was trying to resolve the features referenced by the category.xml with a different qualifier.

If I understand update sites/p2 repositories correctly, it should be possible to offer any artifacts / bundles / features in various flavors, right?

How can I solve this, or rather: can I have a single tycho build that runs the above build steps consecutively with the same qualifier for all?

Addendum: This existing question goes in the same direction and suggests to "install the (feature) Tycho project(s) into ... local Maven repository". That's actually what I'm doing when I run 1. and 2. after each other, specifiying the same local repo for both. But then 3. fails to pull the referenced artifacts from there, because the qualifier is different (two distinct reactor builds). Running everything in the same reactor build would be totally fine for me, but I think that's not possible, because there are different target platforms involved.

I think the solution there is pretty close to what I need, but I don't understand how my category.xml (or site.xml) and the extra dependencies in POM work together. Do I have to abandon category.xml altogether and respecify all my dependencies in the eclipse-repository POM?

My build roughly looks like this:

foo.releng/pom.xml (parent POM)

I need to get absolute path of existing directory and change one of it's property. I wrote simple script for this task and everything works great on my linux machine.

There is an Eclipse RCP/IDE-Plug-in project which depends on several Eclipse Modules like org.eclipse.e4.core.di or org.eclipse.core.runtime.

This project compiles in a Eclipse IDE for Committers environment with a .target file for dependency setup.

I want to add a headless maven/tycho build for this project resulting in errors as follows:

I have an E4 project that contains a product and a plugin. When building the plugin based application using Tycho I get the following error.

I'm creating a maven project from my Eclipse E4 application (product and feature project). After searching some tutorials I got three maven file that imports all the dependencies. One maven file for the feature project, one for the product project and one parent.

My target definition looks like:

I have a very simple Tycho reactor with two modules: one is a standard Maven project with this addition to make it a bundle: