Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms. Affected Versions: jbosstools 4.28.0.AM1 jbt TPs 4.28.0.AM1-SNAPSHOT central TPs 4.28.0.AM1-SNAPSHOT Detail / Summary: Updated : lsp4mp 0.7.1 orbit S202304261239 m2e 2.3.0.20230508-2140 simrel 202305061001-Simrel.2023-06-M2 buildship 3.1.7.v20230428-1350 cdt 11.1.1 jetty 10.0.15 webtools S-3.30M2a-20230502092147 docker 5.11.0.202305022342 reddeer 4.6.0.M2 wildwebdeveloper 1.1.0 eclipse I20230506-1800-M2 qute-jdt 0.14.1 quarkus-jdt 0.14.1 jgit 6.6.0.202305031100-m2 Related JIRA(s): https://issues.redhat.com/browse/JBIDE-28990 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/409 https://github.com/jbosstools/jbosstools-build-ci/pull/225 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.AM1-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.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------