Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms. Affected Versions: jbosstools 4.28.0.Final jbt TPs 4.28.0.Final-SNAPSHOT central TPs 4.28.0.AM1-SNAPSHOT Detail / Summary: Updated: lsp4mp 0.8.0 lsp4e 0.23.0 reddeer 4.6.0 swtbot 4.1.0 docker 5.11.0 webtools 3.30.0 cdt 11.2.0 tm 4.5.500 dtp 1.15.0 simrel 2023-06 GA m2e 2.3.0 orbit R for 4.28 wildwebdeveloper 1.1.1 eclipse 4.28 qute-jdt 0.15.0 quarkus-jdt 0.15.0 jgit 6.6.0 Related JIRA(s): https://issues.redhat.com/browse/JBIDE-29030 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/410 https://github.com/jbosstools/jbosstools-build/pull/346 https://github.com/jbosstools/jbosstools-build-ci/pull/226 https://gitlab.cee.redhat.com/codeready-studio/cci-config/-/merge_request... p2diff Report(s): attached to JIRA ---------- Please review the above changes, as they have been applied and are building today. Once the target platform is built, jobs and parent pom will be updated to point TARGET_PLATFORM_VERSION_MAX at the new version, 4.28.0.Final-SNAPSHOT. You can use the following to build & test the target platforms locally against your component(s). Build target-platform: cd /path/to/jbosstools-target-platforms git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD # or, using hub for git git checkout <pull-request-URL> mvn clean install -f jbosstools/multiple/pom.xml Then, to test the new multiple target platform against your component's build: cd /path/to/your/jbosstools-component mvn clean verify -Dtpc.version=4.28.0.Final-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------