Mickael Istria

I don't think you'll need to change many other projects. The very vast majority of them wouldn't have Platform specific artifacts, and I don't have the impression fixing those is...

@chirontt OK, thanks for the details. So if you have things that you could already contribute, please do so and we'll see what we can merge easily. But at some...

Some of the CI issues such as the ones about not found bundles in https://ci.eclipse.org/equinox/job/equinox/job/PR-121/1/console are caused by the missing win32/win32/aarch64 declaration in the parent pom: https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse-platform-parent/pom.xml#L254 . Please try...

I think it's OK to move it.

I have other priorities at the moment, I won't be able to deal with this move. I've sent on the mailing-lists steps I've used so that anyone should be able...

jdt.doc.isv as well. But I see content in parent pom at https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse.platform.common/pom.xml which seems to be common to all docs bundles. Do we want to un-factorize this part? (I personally...

IMO, it's better to migrate do both or none here. Migrating just one would make things a bit inconsistent and I don't think it would actually help overall.

> Why? Imagine some contributor saying "I want to contribute to JDT doc". The current state is to just go to the right repo and edit it. If we split,...

> You seem to asume that the user already know what is "the right repo" No. I also think about reviewers (us) who, if a user wants to contribute to...

Technically, what can be done for M/RC is to push them to a staging respository under oss.sonatype.org Nexus instance and let consumers use this repository until it's replaced by a...